Skip to main content
The Call External Pipeline index stage sends each document to an index pipeline on another Lucidworks Search or Fusion instance. For example, you can use one instance to crawl and parse content, then send the documents to a different instance for indexing.
This stage is different from the Call Pipeline index stage, which calls another index pipeline in the same Fusion environment.
The stage sends each document to this endpoint on the target instance, using the user name and password for HTTP basic authentication:
The target pipeline processes the document and indexes it in the target collection. The stage doesn’t receive any data back, so changes that the target pipeline makes to the document don’t return to the local pipeline. After sending the document, the stage passes the original, unchanged document to the next stage in the local pipeline. If the local pipeline includes a Solr Indexer stage, the document is also indexed locally, so a copy exists in both instances. Use a dedicated user with the minimum required permissions on the target instance, not an admin user.

​
Micro batching

By default, the stage sends one document at a time and waits for each request to finish. When you enable Micro batching, the stage buffers documents and sends them in batches. Batched documents are sent asynchronously and in no particular order. In batch mode, a failed request doesn’t necessarily cause the original document to fail in the local pipeline. Check the indexing logs for errors.

​
Proxy and certificate settings

To reach the target instance through an HTTP proxy, set Proxy and Proxy Port. If you leave Proxy Port blank, the stage uses port 80. If the proxy requires authentication, set both Proxy User and Proxy Password. The stage fails validation if only one of them is set. If the target instance uses a self-signed or corporate CA certificate, paste the certificate in PEM format in the Certificate field.

​
Configuration

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.