XML Configuration Reference : Consolidation : ConsolidationConfig
 
ConsolidationConfig
com.exalead.mercury.mami.consolidation.v10.ConsolidationConfig
Consolidation Server configuration. The Consolidation Server collects documents from a push API. The document goes through the following transformation steps before being sent to the Indexing Server:
1. Transformation processors
2. Aggregation processors
Attributes:
Name
Type
Default value
Description
name
string
Identifies this consolidation configuration uniquely
nbThreads
int
4
Number of threads to allocate during the transformation and aggregation phases.
maxNativeMemoryConsumptionThreshold
enum(disabled, enabled, auto)
enabled
When reaching the memory consumption value specified, transformation is stopped and transformed documents are committed. Then the transformation starts again.
Enabled: Commits when the memory usage reaches the threshold value specified (by default, 2048 MB).
Auto: Commits when the memory usage reaches 2048 MB.'
maxNativeMemoryConsumptionInMB
int
2048
The maximum of native memory the transformation service can allocate. Reaching this limit triggers a commit.
Nested elements:
Name
Type
Description
CommitTriggerConditions
com.exalead.mercury.mami.indexing.v10.CommitTriggerCondition*
AggregationTriggerConditions
com.exalead.mercury.mami.indexing.v10.CommitTriggerCondition*
AdvancedConfig
com.exalead.mercury.mami.consolidation.v10.AdvancedConfig
AggregationForwardProcessorConfigList
com.exalead.mercury.mami.consolidation.v10.AggregationForwardProcessorConfigList
AggregationProcessorConfigList
com.exalead.mercury.mami.consolidation.v10.AggregationProcessorConfigList
TransformationProcessorConfigList
com.exalead.mercury.mami.consolidation.v10.TransformationProcessorConfigList