This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit a0c030ff8899a9a1e7225c00dd0be6506376822c
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Fri Aug 24 08:51:47 2018 +0200
Regen
---
camel-core/src/main/docs/eips/aggregate-eip.adoc | 2 +-
camel-core/src/main/docs/eips/claimCheck-eip.adoc | 2 +-
.../src/main/docs/eips/hystrixConfiguration-eip.adoc | 14 +++++++-------
camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc | 2 +-
camel-core/src/main/docs/eips/split-eip.adoc | 2 +-
5 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/camel-core/src/main/docs/eips/aggregate-eip.adoc
b/camel-core/src/main/docs/eips/aggregate-eip.adoc
index 01afaf1..b3e0ff6 100644
--- a/camel-core/src/main/docs/eips/aggregate-eip.adoc
+++ b/camel-core/src/main/docs/eips/aggregate-eip.adoc
@@ -37,7 +37,7 @@ The Aggregate EIP supports 25 options which are listed below:
| *strategyMethodAllowNull* | 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. | false | Boolean
| *completionInterval* | A repeating period in millis by which the aggregator
will complete all current aggregated exchanges. Camel has a background task
which is triggered every period. You cannot use this option together with
completionTimeout, only one of them can be used. | | Long
| *completionTimeoutChecker Interval* | Interval in millis that is used by the
background task that checks for timeouts (org.apache.camel.TimeoutMap). By
default the timeout checker runs every second. The timeout is an approximation
and there is no guarantee that the a timeout is triggered exactly after the
timeout value. It is not recommended to use very low timeout values or checker
intervals. | 1000 | Long
-| *completionFromBatchConsumer* | 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. | false | Boolean
+| *completionFromBatchConsumer* | 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 org.apache.camel.Exchange#BATCH_COMPLETE when
its complete. | false | Boolean
| *completionOnNewCorrelation Group* | Enables completion on all previous
groups when a new incoming correlation group. This can for example be used to
complete groups with same correlation keys when they are in consecutive order.
Notice when this is enabled then only 1 correlation group can be in progress as
when a new correlation group starts, then the previous groups is forced
completed. | false | Boolean
| *groupExchanges* | *Deprecated* 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. | false | Boolean
| *eagerCheckCompletion* | Use eager completion checking which means that the
completionPredicate will use the incoming Exchange. As opposed to without eager
completion checking the completionPredicate will use the aggregated Exchange. |
false | Boolean
diff --git a/camel-core/src/main/docs/eips/claimCheck-eip.adoc
b/camel-core/src/main/docs/eips/claimCheck-eip.adoc
index 8693def..b75fce9 100644
--- a/camel-core/src/main/docs/eips/claimCheck-eip.adoc
+++ b/camel-core/src/main/docs/eips/claimCheck-eip.adoc
@@ -21,7 +21,7 @@ The Claim Check EIP supports 5 options which are listed below:
| Name | Description | Default | Type
| *operation* | *Required* The claim check operation to use. The following
operations is supported: Get - Gets (does not remove) the claim check by the
given key. GetAndRemove - Gets and remove the claim check by the given key. Set
- Sets a new (will override if key already exists) claim check with the given
key. Push - Sets a new claim check on the stack (does not use key). Pop - Gets
the latest claim check from the stack (does not use key). | |
ClaimCheckOperation
| *key* | To use a specific key for claim check id. | | String
-| *filter* | Specified a filter to control what data gets merging data back
from the claim check repository. The following syntax is supported: body - to
aggregate the message body attachments - to aggregate all the message
attachments headers - to aggregate all the message headers header:pattern - to
aggregate all the message headers that matches the pattern. The pattern syntax
is documented by: link EndpointHelpermatchPattern(String, String). You can
specify multiple rules separated by [...]
+| *filter* | Specified a filter to control what data gets merging data back
from the claim check repository. The following syntax is supported: body - to
aggregate the message body attachments - to aggregate all the message
attachments headers - to aggregate all the message headers header:pattern - to
aggregate all the message headers that matches the pattern. The pattern syntax
is documented by: link EndpointHelper#matchPattern(String, String). You can
specify multiple rules separated b [...]
| *strategyRef* | To use a custom AggregationStrategy instead of the default
implementation. Notice you cannot use both custom aggregation strategy and
configure data at the same time. | | String
| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
|===
diff --git a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
index b743fcd..4d595b9 100644
--- a/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
+++ b/camel-core/src/main/docs/eips/hystrixConfiguration-eip.adoc
@@ -12,14 +12,14 @@ The Hystrix Configuration EIP supports 31 options which are
listed below:
| *threadPoolKey* | Sets the thread pool key to use. Will by default use the
same value as groupKey has been configured to use. | CamelHystrix | String
| *circuitBreakerEnabled* | Whether to use a HystrixCircuitBreaker or not. If
false no circuit-breaker logic will be used and all requests permitted. This is
similar in effect to circuitBreakerForceClosed() except that continues tracking
metrics and knowing whether it should be open/closed, this property results in
not even instantiating a circuit-breaker. | true | Boolean
| *circuitBreakerError ThresholdPercentage* | Error percentage threshold (as
whole number such as 50) at which point the circuit breaker will trip open and
reject requests. It will stay tripped for the duration defined in
circuitBreakerSleepWindowInMilliseconds; The error percentage this is compared
against comes from HystrixCommandMetrics.getHealthCounts(). | 50 | Integer
-| *circuitBreakerForceClosed* | If true the
HystrixCircuitBreakerallowRequest() will always return true to allow requests
regardless of the error percentage from
HystrixCommandMetrics.getHealthCounts(). The circuitBreakerForceOpen() property
takes precedence so if it set to true this property does nothing. | false |
Boolean
+| *circuitBreakerForceClosed* | If true the
HystrixCircuitBreaker#allowRequest() will always return true to allow requests
regardless of the error percentage from
HystrixCommandMetrics.getHealthCounts(). The circuitBreakerForceOpen() property
takes precedence so if it set to true this property does nothing. | false |
Boolean
| *circuitBreakerForceOpen* | If true the HystrixCircuitBreaker.allowRequest()
will always return false, causing the circuit to be open (tripped) and reject
all requests. This property takes precedence over circuitBreakerForceClosed();
| false | Boolean
| *circuitBreakerRequestVolume Threshold* | Minimum number of requests in the
metricsRollingStatisticalWindowInMilliseconds() that must exist before the
HystrixCircuitBreaker will trip. If below this number the circuit will not trip
regardless of error percentage. | 20 | Integer
| *circuitBreakerSleepWindow InMilliseconds* | The time in milliseconds after
a HystrixCircuitBreaker trips open that it should wait before trying requests
again. | 5000 | Integer
| *executionIsolationSemaphore MaxConcurrentRequests* | Number of concurrent
requests permitted to HystrixCommand.run(). Requests beyond the concurrent
limit will be rejected. Applicable only when executionIsolationStrategy ==
SEMAPHORE. | 20 | Integer
| *executionIsolationStrategy* | What isolation strategy HystrixCommand.run()
will be executed with. If THREAD then it will be executed on a separate thread
and concurrent requests limited by the number of threads in the thread-pool. If
SEMAPHORE then it will be executed on the calling thread and concurrent
requests limited by the semaphore count. | THREAD | String
-| *executionIsolationThread InterruptOnTimeout* | Whether the execution thread
should attempt an interrupt (using link Futurecancel) when a thread times out.
Applicable only when executionIsolationStrategy() == THREAD. | true | Boolean
-| *executionTimeoutIn Milliseconds* | Time in milliseconds at which point the
command will timeout and halt execution. If link
executionIsolationThreadInterruptOnTimeout == true and the command is
thread-isolated, the executing thread will be interrupted. If the command is
semaphore-isolated and a HystrixObservableCommand, that command will get
unsubscribed. | 1000 | Integer
+| *executionIsolationThread InterruptOnTimeout* | Whether the execution thread
should attempt an interrupt (using Future#cancel) when a thread times out.
Applicable only when executionIsolationStrategy() == THREAD. | true | Boolean
+| *executionTimeoutIn Milliseconds* | Time in milliseconds at which point the
command will timeout and halt execution. If
executionIsolationThreadInterruptOnTimeout == true and the command is
thread-isolated, the executing thread will be interrupted. If the command is
semaphore-isolated and a HystrixObservableCommand, that command will get
unsubscribed. | 1000 | Integer
| *executionTimeoutEnabled* | Whether the timeout mechanism is enabled for
this command | true | Boolean
| *fallbackIsolationSemaphore MaxConcurrentRequests* | Number of concurrent
requests permitted to HystrixCommand.getFallback(). Requests beyond the
concurrent limit will fail-fast and not attempt retrieving a fallback. | 10 |
Integer
| *fallbackEnabled* | Whether HystrixCommand.getFallback() should be attempted
when failure occurs. | true | Boolean
@@ -31,11 +31,11 @@ The Hystrix Configuration EIP supports 31 options which are
listed below:
| *metricsRollingStatistical WindowInMilliseconds* | This property sets the
duration of the statistical rolling window, in milliseconds. This is how long
metrics are kept for the thread pool. The window is divided into buckets and
rolls by those increments. | 10000 | Integer
| *metricsRollingStatistical WindowBuckets* | Number of buckets the rolling
statistical window is broken into. This is passed into HystrixRollingNumber
inside HystrixCommandMetrics. | 10 | Integer
| *requestLogEnabled* | Whether HystrixCommand execution and events should be
logged to HystrixRequestLog. | true | Boolean
-| *corePoolSize* | Core thread-pool size that gets passed to link
java.util.concurrent.ThreadPoolExecutorsetCorePoolSize(int) | 10 | Integer
-| *maximumSize* | Maximum thread-pool size that gets passed to link
ThreadPoolExecutorsetMaximumPoolSize(int). This is the maximum amount of
concurrency that can be supported without starting to reject HystrixCommands.
Please note that this setting only takes effect if you also set
allowMaximumSizeToDivergeFromCoreSize | 10 | Integer
-| *keepAliveTime* | Keep-alive time in minutes that gets passed to link
ThreadPoolExecutorsetKeepAliveTime(long, TimeUnit) | 1 | Integer
+| *corePoolSize* | Core thread-pool size that gets passed to
java.util.concurrent.ThreadPoolExecutor#setCorePoolSize(int) | 10 | Integer
+| *maximumSize* | Maximum thread-pool size that gets passed to
ThreadPoolExecutor#setMaximumPoolSize(int). This is the maximum amount of
concurrency that can be supported without starting to reject HystrixCommands.
Please note that this setting only takes effect if you also set
allowMaximumSizeToDivergeFromCoreSize | 10 | Integer
+| *keepAliveTime* | Keep-alive time in minutes that gets passed to link
ThreadPoolExecutor#setKeepAliveTime(long, TimeUnit) | 1 | Integer
| *maxQueueSize* | Max queue size that gets passed to BlockingQueue in
HystrixConcurrencyStrategy.getBlockingQueue(int) This should only affect the
instantiation of a threadpool - it is not eliglible to change a queue size on
the fly. For that, use queueSizeRejectionThreshold(). | -1 | Integer
-| *queueSizeRejectionThreshold* | Queue size rejection threshold is an
artificial max size at which rejections will occur even if link maxQueueSize
has not been reached. This is done because the link maxQueueSize of a
BlockingQueue can not be dynamically changed and we want to support dynamically
changing the queue size that affects rejections. This is used by HystrixCommand
when queuing a thread for execution. | 5 | Integer
+| *queueSizeRejectionThreshold* | Queue size rejection threshold is an
artificial max size at which rejections will occur even if maxQueueSize has not
been reached. This is done because the maxQueueSize of a BlockingQueue can not
be dynamically changed and we want to support dynamically changing the queue
size that affects rejections. This is used by HystrixCommand when queuing a
thread for execution. | 5 | Integer
| *threadPoolRollingNumber StatisticalWindowIn Milliseconds* | Duration of
statistical rolling window in milliseconds. This is passed into
HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10000 |
Integer
| *threadPoolRollingNumber StatisticalWindowBuckets* | Number of buckets the
rolling statistical window is broken into. This is passed into
HystrixRollingNumber inside each HystrixThreadPoolMetrics instance. | 10 |
Integer
| *allowMaximumSizeToDiverge FromCoreSize* | Allows the configuration for
maximumSize to take effect. That value can then be equal to, or higher, than
coreSize | false | Boolean
diff --git a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
index 4516f2f..5381a69 100644
--- a/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
+++ b/camel-core/src/main/docs/eips/idempotentConsumer-eip.adoc
@@ -46,7 +46,7 @@ The Idempotent Consumer EIP supports 5 options which are
listed below:
| *messageIdRepositoryRef* | *Required* Sets the reference name of the message
id repository | | String
| *eager* | Sets whether to eagerly add the key to the idempotent repository
or wait until the exchange is complete. Eager is default enabled. | true |
Boolean
| *completionEager* | Sets whether to complete the idempotent consumer eager
or when the exchange is done. If this option is true to complete eager, then
the idempotent consumer will trigger its completion when the exchange reached
the end of the block of the idempotent consumer pattern. So if the exchange is
continued routed after the block ends, then whatever happens there does not
affect the state. If this option is false (default) to not complete eager, then
the idempotent consumer w [...]
-| *skipDuplicate* | Sets whether to skip duplicates or not. The default
behavior is to skip duplicates. A duplicate message would have the Exchange
property link org.apache.camel.ExchangeDUPLICATE_MESSAGE set to a link
BooleanTRUE value. A none duplicate message will not have this property set. |
true | Boolean
+| *skipDuplicate* | Sets whether to skip duplicates or not. The default
behavior is to skip duplicates. A duplicate message would have the Exchange
property org.apache.camel.Exchange#DUPLICATE_MESSAGE set to a Boolean#TRUE
value. A none duplicate message will not have this property set. | true |
Boolean
| *removeOnFailure* | Sets whether to remove or keep the key on failure. The
default behavior is to remove the key on failure. | true | Boolean
|===
// eip options: END
diff --git a/camel-core/src/main/docs/eips/split-eip.adoc
b/camel-core/src/main/docs/eips/split-eip.adoc
index 5364f39..a365137 100644
--- a/camel-core/src/main/docs/eips/split-eip.adoc
+++ b/camel-core/src/main/docs/eips/split-eip.adoc
@@ -19,7 +19,7 @@ The Split EIP supports 12 options which are listed below:
| *strategyMethodName* | This option can be used to explicit declare the
method name to use, when using POJOs as the AggregationStrategy. | | String
| *strategyMethodAllowNull* | If this option is false then the aggregate
method is not used if there was no data to enrich. If this option is true then
null values is used as the oldExchange (when no data to enrich), when using
POJOs as the AggregationStrategy | false | Boolean
| *executorServiceRef* | Refers to a custom Thread Pool to be used for
parallel processing. Notice if you set this option, then parallel processing is
automatic implied, and you do not have to enable that option as well. | |
String
-| *streaming* | When in streaming mode, then the splitter splits the original
message on-demand, and each splitted message is processed one by one. This
reduces memory usage as the splitter do not split all the messages first, but
then we do not know the total size, and therefore the link
org.apache.camel.ExchangeSPLIT_SIZE is empty. In non-streaming mode (default)
the splitter will split each message first, to know the total size, and then
process each message one by one. This requires [...]
+| *streaming* | When in streaming mode, then the splitter splits the original
message on-demand, and each splitted message is processed one by one. This
reduces memory usage as the splitter do not split all the messages first, but
then we do not know the total size, and therefore the
org.apache.camel.Exchange#SPLIT_SIZE is empty. In non-streaming mode (default)
the splitter will split each message first, to know the total size, and then
process each message one by one. This requires to k [...]
| *stopOnException* | Will now stop further processing if an exception or
failure occurred during processing of an org.apache.camel.Exchange and the
caused exception will be thrown. Will also stop if processing the exchange
failed (has a fault message) or an exception was thrown and handled by the
error handler (such as using onException). In all situations the splitter will
stop further processing. This is the same behavior as in pipeline, which is
used by the routing engine. The defaul [...]
| *timeout* | Sets a total timeout specified in millis, when using parallel
processing. If the Splitter hasn't been able to split and process all the sub
messages within the given timeframe, then the timeout triggers and the Splitter
breaks out and continues. Notice if you provide a
TimeoutAwareAggregationStrategy then the timeout method is invoked before
breaking out. If the timeout is reached with running tasks still remaining,
certain tasks for which it is difficult for Camel to shut [...]
| *onPrepareRef* | Uses the Processor when preparing the
org.apache.camel.Exchange to be send. This can be used to deep-clone messages
that should be send, or any custom logic needed before the exchange is send. |
| String
