Trigger and Synchronize Consolidation

This section describes how consolidated data is sent to the index.

See Also
Configuring the Processors
Forwarding Documents to Other Build Groups

Commit triggers define when to write documents to the index. You can link commit conditions to inactivity, number, or size of documents, or elapsed time.

Aggregation triggers define when transformed documents and documents stored or synchronized in the Consolidation Server storage are aggregated. You can also link these conditions to inactivity, number, or size of documents, or elapsed time. Once complete, the result of the aggregation job is sent to the target Indexing Server specified in the Forward rules section.

When launching a Force commit operation, you commit the transformation job and then start an aggregation.

Important: By default, a connector does not send a synchronization order to the Consolidation Server when its scan is finished. To enable this behavior, go to Connectors > Deployment > Push API and select the Force indexing after scan option.