The Solr Update Parser stage parses Solr’s “update” messages and transforms them into Fusion PipelineDocuments. This makes it possible to integrate with existing datasets that happen to be in Solr’s “update” format and send them to an index pipeline. This parser stage supports XML, JSON, CSV and JavaBin. Fusion can also integrate with Solr “update” documents using the SolrXML connector, but the connector only supports XML.
When parsing CSV files, consider using the CSV parser, which provides more options than the Solr Update Parser. All CSV files are treated the same in terms of structure and schema.
To learn more about how Fusion’s Solr core indexes “update” documents, see the Solr Reference Guide. The https://FUSION_HOST:FUSION_PORT/apps/solr-dist/example/exampledocs/ directory contains many of these “update” format documents. Fusion also ships with a https://FUSION_HOST:FUSION_PORT/apps/solr-dist/bin/post utility which is used to index documents from the file system. However, the post utility has no way of integrating with Fusion; its output is sent directly to Solr.
When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.