To use a org.apache.camel.processor.aggregate.AggregateController to allow
external sources to control this aggregator.

Sets the custom aggregate repository to use Will by default use
org.apache.camel.processor.aggregate.MemoryAggregationRepository

Closes a correlation key when its complete. Any late received exchanges which
has a correlation key that has been closed it will be defined and a
ClosedCorrelationKeyException is thrown.

Indicates to wait to complete all current and partial (pending) aggregated
exchanges when the context is stopped. This also means that we will wait for all
pending exchanges which are stored in the aggregation repository to complete so
the repository is empty before we can stop. You may want to enable this when
using the memory based aggregation repository that is memory based only and do
not store data on disk. When this option is enabled then the aggregator is
waiting to complete all those exchanges before its stopped when stopping
CamelContext or the route using it.

Enables the batch completion mode where we aggregate from a
org.apache.camel.BatchConsumer and aggregate the total number of exchanges the
org.apache.camel.BatchConsumer has reported as total by checking the exchange
property link org.apache.camel.ExchangeBATCH_COMPLETE when its complete.

Sets the completion interval which would cause the aggregate to consider the
group as complete and send out the aggregated exchange.

Sets the completion size which is the number of aggregated exchanges which would
cause the aggregate to consider the group as complete and send out the
aggregated exchange.

Sets the completion timeout which would cause the aggregate to consider the
group as complete and send out the aggregated exchange.

Discards the aggregated message on completion timeout. This means on timeout the
aggregated message is dropped and not sent out of the aggregator.

Use eager completion checking which means that the completionPredicate will use
the incoming Exchange. At opposed to without eager completion checking the
completionPredicate will use the aggregated Exchange.

If using parallelProcessing you can specify a custom thread pool to be used. In
fact also if you are not using parallelProcessing this custom thread pool is
used to send out aggregated exchanges as well.

Indicates to complete all current aggregated exchanges when the context is
stopped

Enables grouped exchanges so the aggregator will group all aggregated exchanges
into a single combined Exchange holding all the aggregated exchanges in a
java.util.List.

Sets the id of this node

If a correlation key cannot be successfully evaluated it will be ignored by
logging a DEBUG and then just ignore the incoming Exchange.

Turns on using optimistic locking which requires the aggregationRepository being
used is supporting this by implementing
org.apache.camel.spi.OptimisticLockingAggregationRepository.

When aggregated are completed they are being send out of the aggregator. This
option indicates whether or not Camel should use a thread pool with multiple
threads for concurrency. If no custom thread pool has been specified then Camel
creates a default pool with 10 concurrent threads.

If this option is false then the aggregate method is not used for the very first
aggregation. If this option is true then null values is used as the oldExchange
(at the very first aggregation) when using POJOs as the AggregationStrategy.

This option can be used to explicit declare the method name to use when using
POJOs as the AggregationStrategy.

A reference to lookup the AggregationStrategy in the Registry. Configuring an
AggregationStrategy is required and is used to merge the incoming Exchange with
the existing already merged exchanges. At first call the oldExchange parameter
is null. On subsequent invocations the oldExchange contains the merged exchanges
and newExchange is of course the new incoming Exchange.

If using either of the completionTimeout completionTimeoutExpression or
completionInterval options a background thread is created to check for the
completion for every aggregator. Set this option to provide a custom thread pool
to be used rather than creating a new thread for every aggregator.