PipelineDocument
objects for indexing by Managed Fusion-managed Solr service.
An index pipeline consists of a series of configurable
index pipeline stages,
each performing a different transformation on the data before passing the result to the next stage in the pipeline.
The final stage is the
Solr Indexer stage,
which transforms the PipelineDocument into a Solr document and submits it to Solr for indexing in a specific
Collection.
Each configured datasource has an associated index pipeline and uses a
connector
to fetch data to parse and then input into the index pipeline.
Import Data with the REST API
application/json
as the content type. If your JSON file is a list or array of many items, the endpoint operates in a streaming way and indexes the docs as necessary.?echo=false
to the URL.Be sure to set the content type header properly for the content being sent. Some frequently used content types are:application/json
, application/xml
application/pdf
application/vnd.openxmlformats-officedocument.wordprocessingml.document
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet
application/vnd.vnd.openxmlformats-officedocument.presentationml.presentation
$FUSION_HOME/apps/solr-dist/example/exampledocs
you can find a few sample documents. This example uses one of these, books.json
.To push JSON data to an index profile under an app:books.json
, enter the following, substituting your values for username, password, and index profile name:
\*:*
.author
and name
.https://EXAMPLE_COMPANY.b.lucidworks.cloud/api/index-pipelines/INDEX_PIPELINE/collections/COLLECTION_NAME/index?parserId=PARSER
.If you do not specify a parser, and you are indexing outside of an app (https://EXAMPLE_COMPANY.b.lucidworks.cloud/api/index-pipelines/...
), then the _system
parser is used.If you do not specify a parser, and you are indexing in an app context (https://EXAMPLE_COMPANY.b.lucidworks.cloud/api/apps/APP_NAME/index-pipelines/...
), then the parser with the same name as the app is used.