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.

JSON parsing converts JSON content from a single document field into one or more new documents. This parser uses Solr’s JsonRecordReader to split JSON into sub-documents. If your JSON file contains a column named id, this column is consumed to populate the document’s unique identifier (Solr’s uniqueKey) and is not available as a stored field. This behavior occurs because the default value of the parser’s Document ID Source Field parameter is also id. When a CSV column matches this parameter:
  • The column’s value is used to generate the document ID.
  • The column does not appear in the indexed document as a field.
If you need to preserve your id column data as a regular field, use one of these options:
  • Change the column header from id to another name such as record_id or item_id. This is the simplest solution.
  • In the JSON parser stage configuration, use a mapping rule to map $.id to another name such as record_id or item_id.
  • In the Index Workbench’s parser configuration, set the Document ID Source Field to a different column name. This allows id to be treated as a normal field, but you must specify a different column to use as the document identifier.
See Parsers Overview for information about configuring the Document ID Source Field parameter.
  • 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.
  • Enter the root path in Unix command-line format, not JSON format. For example, enter /response/docs, not $['response']['docs'].