Processor Action Context

You have to define an action context for each processor in the Consolidation Server pipeline.

There are two different action contexts to specify the action performed on documents:

  • create/update: to create or update documents coming from one or more connectors or the Consolidation Store.

  • delete: to delete documents from the connectors or the Consolidation Store.

This page discusses:

Delete Action Context

This is what occurs in the Consolidation Server when connectors push delete orders to remove documents from the Indexing Server:

  • If you defined a processor with a delete action context that matches the document types, the processor code is executed and yields to the next processor or stage, unless a discard operation is specified.

  • If you did not define a processor with a delete action context, or if it does not match the document types, the document proceeds as if a default processor was defined with auto-yielding. This behavior is true for both transformation and aggregation phases.

In other words, unless a delete processor has been defined and matches the document types, when connectors push delete orders, the Consolidation Server:

1. Pushes a delete order to the Consolidation Store and removes documents from it.

2. Pushes delete orders to the Indexing Servers and removes them from the Indexing Store.

In addition, default delete orders are also applied to all child documents.

Delete Orders in Create/Update Action Context

You can also perform delete orders in a create/update action context, using deleteDocument operations. This is mostly in the Aggregation Phase that such operations can be useful. Indeed, we recommend controlling the presence of documents in the Consolidation Store with orders coming from the connectors.