Skip to main content

Documentation Index

Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt

Use this file to discover all available pages before exploring further.

The Solr Update Parser stage parses Solr’s “update” messages and transforms them into Lucidworks Search 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.
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.
The https://EXAMPLE_COMPANY.lucidworks.cloud/apps/solr-dist/example/exampledocs/ directory contains many of these “update” format documents. Lucidworks Search also ships with a https://EXAMPLE_COMPANY.lucidworks.cloud/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 Lucidworks Search; its output is sent directly to Solr.
Replace EXAMPLE_COMPANY with the name provided by your Lucidworks representative.
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.