This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
The following commit(s) were added to refs/heads/master by this push:
new 58a8aad [create-pull-request] automated change
58a8aad is described below
commit 58a8aad7b36bdadefc703cbe215dd465a0c365e2
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Sep 17 01:13:14 2020 +0000
[create-pull-request] automated change
---
.../src/main/docs/azure-eventhubs-starter.adoc | 4 ++--
components-starter/camel-corda-starter/pom.xml | 8 --------
.../camel-ftp-starter/src/main/docs/ftp-starter.adoc | 6 +++---
.../camel-grok-starter/src/main/docs/grok-starter.adoc | 2 +-
components-starter/camel-iota-starter/pom.xml | 12 ------------
.../camel-kafka-starter/src/main/docs/kafka-starter.adoc | 2 +-
docs/modules/ROOT/pages/azure-eventhubs-starter.adoc | 4 ++--
docs/modules/ROOT/pages/ftp-starter.adoc | 6 +++---
docs/modules/ROOT/pages/grok-starter.adoc | 2 +-
docs/modules/ROOT/pages/kafka-starter.adoc | 2 +-
10 files changed, 14 insertions(+), 34 deletions(-)
diff --git
a/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
b/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
index b0c7150..dc845e2 100644
---
a/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
+++
b/components-starter/camel-azure-eventhubs-starter/src/main/docs/azure-eventhubs-starter.adoc
@@ -35,14 +35,14 @@ The component supports 22 options, which are listed below.
| *camel.component.azure-eventhubs.checkpoint-store* | Sets the
CheckpointStore the EventProcessorClient will use for storing partition
ownership and checkpoint information. Users can, optionally, provide their own
implementation of CheckpointStore which will store ownership and checkpoint
information. By default it set to use
com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which
stores all checkpoint offsets into Azure Blob Storage. The option is a
com.azure.messa [...]
| *camel.component.azure-eventhubs.configuration* | The component
configurations. The option is a
org.apache.camel.component.azure.eventhubs.EventHubsConfiguration type. | |
String
| *camel.component.azure-eventhubs.connection-string* | Instead of supplying
namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the
connection string for your eventHub. The connection string for EventHubs
already include all the necessary information to connection to your EventHub.
To learn on how to generate the connection string, take a look at this
documentation:
\https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string
| | String
-| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the
consumer group this consumer is associated with. Events are read in the context
of this group. The name of the consumer group that is created by default is
{link #DEFAULT_CONSUMER_GROUP_NAME \$Default}. | $Default | String
+| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the
consumer group this consumer is associated with. Events are read in the context
of this group. The name of the consumer group that is created by default is
{link #DEFAULT_CONSUMER_GROUP_NAME $Default}. | $Default | String
| *camel.component.azure-eventhubs.enabled* | Whether to enable auto
configuration of the azure-eventhubs component. This is enabled by default. |
| Boolean
| *camel.component.azure-eventhubs.event-position* | Sets the map containing
the event position to use for each partition if a checkpoint for the partition
does not exist in CheckpointStore. This map is keyed off of the partition id.
If there is no checkpoint in CheckpointStore and there is no entry in this map,
the processing of the partition will start from {link EventPosition#latest()
latest} position. | | Map
| *camel.component.azure-eventhubs.lazy-start-producer* | Whether the producer
should be started lazy (on the first message). By starting lazy you can use
this to allow CamelContext and routes to startup in situations where a producer
may otherwise fail during starting and cause the route to fail being started.
By deferring this startup to be lazy then the startup failure can be handled
during routing messages via Camel's routing error handlers. Beware that when
the first message is proc [...]
| *camel.component.azure-eventhubs.partition-id* | Sets the identifier of the
Event Hub partition that the {link EventData events} will be sent to. If the
identifier is not specified, the Event Hubs service will be responsible for
routing events that are sent to an available partition. | | String
| *camel.component.azure-eventhubs.partition-key* | Sets a hashing key to be
provided for the batch of events, which instructs the Event Hubs service to map
this key to a specific partition. The selection of a partition is stable for a
given partition hashing key. Should any other batches of events be sent using
the same exact partition hashing key, the Event Hubs service will route them
all to the same partition. This should be specified only when there is a need
to group events by part [...]
| *camel.component.azure-eventhubs.prefetch-count* | Sets the count used by
the receiver to control the number of events the Event Hub consumer will
actively receive and queue locally without regard to whether a receive
operation is currently active. | 500 | Integer
-| *camel.component.azure-eventhubs.producer-async-client* | Sets the
EventHubProducerAsyncClient.An asynchronous producer responsible for
transmitting EventData to a specific Event Hub, grouped together in batches.
Depending on the {link CreateBatchOptions options} specified when creating an
\{linkEventDataBatch\}, the events may be automatically routed to an available
partition or specific to a partition. Use by this component to produce the data
in camel producer. The option is a com.a [...]
+| *camel.component.azure-eventhubs.producer-async-client* | Sets the
EventHubProducerAsyncClient.An asynchronous producer responsible for
transmitting EventData to a specific Event Hub, grouped together in batches.
Depending on the {link CreateBatchOptions options} specified when creating an
\{linkEventDataBatch}, the events may be automatically routed to an available
partition or specific to a partition. Use by this component to produce the data
in camel producer. The option is a com.az [...]
| *camel.component.azure-eventhubs.shared-access-key* | The generated value
for the SharedAccessName | | String
| *camel.component.azure-eventhubs.shared-access-name* | The name you chose
for your EventHubs SAS keys | | String
| *camel.component.azure-eventhubs.basic-property-binding* | *Deprecated*
Whether the component should use basic property binding (Camel 2.x) or the
newer property binding with additional capabilities | false | Boolean
diff --git a/components-starter/camel-corda-starter/pom.xml
b/components-starter/camel-corda-starter/pom.xml
index 43b013d..274f6da 100644
--- a/components-starter/camel-corda-starter/pom.xml
+++ b/components-starter/camel-corda-starter/pom.xml
@@ -41,14 +41,6 @@
<!--START OF GENERATED CODE-->
<exclusions>
<exclusion>
- <groupId>ch.qos.logback</groupId>
- <artifactId>logback-classic</artifactId>
- </exclusion>
- <exclusion>
- <groupId>ch.qos.logback</groupId>
- <artifactId>logback-core</artifactId>
- </exclusion>
- <exclusion>
<groupId>org.apache.logging.log4j</groupId>
<artifactId>log4j-core</artifactId>
</exclusion>
diff --git
a/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
b/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
index 35544d1..f422acd 100644
--- a/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
+++ b/components-starter/camel-ftp-starter/src/main/docs/ftp-starter.adoc
@@ -25,14 +25,14 @@ The component supports 13 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ftp.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.ftp.enabled* | Whether to enable auto configuration of the
\ftp component. This is enabled by default. | | Boolean
+| *camel.component.ftp.enabled* | Whether to enable auto configuration of the
ftp component. This is enabled by default. | | Boolean
| *camel.component.ftp.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then c [...]
| *camel.component.ftps.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.ftps.enabled* | Whether to enable auto configuration of the
\ftps component. This is enabled by default. | | Boolean
+| *camel.component.ftps.enabled* | Whether to enable auto configuration of the
ftps component. This is enabled by default. | | Boolean
| *camel.component.ftps.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then [...]
| *camel.component.ftps.use-global-ssl-context-parameters* | Enable usage of
global SSL context parameters. | false | Boolean
| *camel.component.sftp.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.sftp.enabled* | Whether to enable auto configuration of the
\sftp component. This is enabled by default. | | Boolean
+| *camel.component.sftp.enabled* | Whether to enable auto configuration of the
sftp component. This is enabled by default. | | Boolean
| *camel.component.sftp.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then [...]
| *camel.component.ftp.basic-property-binding* | *Deprecated* Whether the
component should use basic property binding (Camel 2.x) or the newer property
binding with additional capabilities | false | Boolean
| *camel.component.ftps.basic-property-binding* | *Deprecated* Whether the
component should use basic property binding (Camel 2.x) or the newer property
binding with additional capabilities | false | Boolean
diff --git
a/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
b/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
index 4d46e6e..8a65d73 100644
--- a/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
+++ b/components-starter/camel-grok-starter/src/main/docs/grok-starter.adoc
@@ -28,7 +28,7 @@ The component supports 6 options, which are listed below.
| *camel.dataformat.grok.content-type-header* | Whether the data format should
set the Content-Type header with the type from the data format if the data
format is capable of doing so. For example application/xml for data formats
marshalling to XML, or application/json for data formats marshalling to JSON
etc. | false | Boolean
| *camel.dataformat.grok.enabled* | Whether to enable auto configuration of
the grok data format. This is enabled by default. | | Boolean
| *camel.dataformat.grok.flattened* | Turns on flattened mode. In flattened
mode the exception is thrown when there are multiple pattern matches with same
key. | false | Boolean
-| *camel.dataformat.grok.named-only* | Whether to capture named expressions
only or not (i.e. %{IP:ip} but not \$\{IP\}) | false | Boolean
+| *camel.dataformat.grok.named-only* | Whether to capture named expressions
only or not (i.e. %{IP:ip} but not $\{IP}) | false | Boolean
| *camel.dataformat.grok.pattern* | The grok pattern to match lines of input |
| String
|===
// spring-boot-auto-configure options: END
diff --git a/components-starter/camel-iota-starter/pom.xml
b/components-starter/camel-iota-starter/pom.xml
index ce65d0f..2050aee 100644
--- a/components-starter/camel-iota-starter/pom.xml
+++ b/components-starter/camel-iota-starter/pom.xml
@@ -38,18 +38,6 @@
<groupId>org.apache.camel</groupId>
<artifactId>camel-iota</artifactId>
<version>${camel-version}</version>
- <!--START OF GENERATED CODE-->
- <exclusions>
- <exclusion>
- <groupId>ch.qos.logback</groupId>
- <artifactId>logback-classic</artifactId>
- </exclusion>
- <exclusion>
- <groupId>ch.qos.logback</groupId>
- <artifactId>logback-core</artifactId>
- </exclusion>
- </exclusions>
- <!--END OF GENERATED CODE-->
</dependency>
<!--START OF GENERATED CODE-->
<dependency>
diff --git
a/components-starter/camel-kafka-starter/src/main/docs/kafka-starter.adoc
b/components-starter/camel-kafka-starter/src/main/docs/kafka-starter.adoc
index 3c6bd9a..f13910b 100644
--- a/components-starter/camel-kafka-starter/src/main/docs/kafka-starter.adoc
+++ b/components-starter/camel-kafka-starter/src/main/docs/kafka-starter.adoc
@@ -56,7 +56,7 @@ The component supports 98 options, which are listed below.
| *camel.component.kafka.kafka-manual-commit-factory* | Factory to use for
creating KafkaManualCommit instances. This allows to plugin a custom factory to
create custom KafkaManualCommit instances in case special logic is needed when
doing manual commits that deviates from the default implementation that comes
out of the box. The option is a
org.apache.camel.component.kafka.KafkaManualCommitFactory type. | | String
| *camel.component.kafka.kerberos-before-relogin-min-time* | Login thread
sleep time between refresh attempts. | 60000 | Integer
| *camel.component.kafka.kerberos-init-cmd* | Kerberos kinit command path.
Default is /usr/bin/kinit | /usr/bin/kinit | String
-| *camel.component.kafka.kerberos-principal-to-local-rules* | A list of rules
for mapping from principal names to short names (typically operating system
usernames). The rules are evaluated in order and the first rule that matches a
principal name is used to map it to a short name. Any later rules in the list
are ignored. By default, principal names of the form
\{username\}/\{hostname\}\{REALM\} are mapped to \{username\}. For more details
on the format please see the security authorizat [...]
+| *camel.component.kafka.kerberos-principal-to-local-rules* | A list of rules
for mapping from principal names to short names (typically operating system
usernames). The rules are evaluated in order and the first rule that matches a
principal name is used to map it to a short name. Any later rules in the list
are ignored. By default, principal names of the form
\{username}/\{hostname}\{REALM} are mapped to \{username}. For more details on
the format please see the security authorization [...]
| *camel.component.kafka.kerberos-renew-jitter* | Percentage of random jitter
added to the renewal time. | | Double
| *camel.component.kafka.kerberos-renew-window-factor* | Login thread will
sleep until the specified window factor of time from last refresh to ticket's
expiry has been reached, at which time it will try to renew the ticket. | |
Double
| *camel.component.kafka.key* | The record key (or null if no key is
specified). If this option has been configured then it take precedence over
header KafkaConstants#KEY | | String
diff --git a/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
b/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
index b0c7150..dc845e2 100644
--- a/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
+++ b/docs/modules/ROOT/pages/azure-eventhubs-starter.adoc
@@ -35,14 +35,14 @@ The component supports 22 options, which are listed below.
| *camel.component.azure-eventhubs.checkpoint-store* | Sets the
CheckpointStore the EventProcessorClient will use for storing partition
ownership and checkpoint information. Users can, optionally, provide their own
implementation of CheckpointStore which will store ownership and checkpoint
information. By default it set to use
com.azure.messaging.eventhubs.checkpointstore.blob.BlobCheckpointStore which
stores all checkpoint offsets into Azure Blob Storage. The option is a
com.azure.messa [...]
| *camel.component.azure-eventhubs.configuration* | The component
configurations. The option is a
org.apache.camel.component.azure.eventhubs.EventHubsConfiguration type. | |
String
| *camel.component.azure-eventhubs.connection-string* | Instead of supplying
namespace, sharedAccessKey, sharedAccessName ... etc, you can just supply the
connection string for your eventHub. The connection string for EventHubs
already include all the necessary information to connection to your EventHub.
To learn on how to generate the connection string, take a look at this
documentation:
\https://docs.microsoft.com/en-us/azure/event-hubs/event-hubs-get-connection-string
| | String
-| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the
consumer group this consumer is associated with. Events are read in the context
of this group. The name of the consumer group that is created by default is
{link #DEFAULT_CONSUMER_GROUP_NAME \$Default}. | $Default | String
+| *camel.component.azure-eventhubs.consumer-group-name* | Sets the name of the
consumer group this consumer is associated with. Events are read in the context
of this group. The name of the consumer group that is created by default is
{link #DEFAULT_CONSUMER_GROUP_NAME $Default}. | $Default | String
| *camel.component.azure-eventhubs.enabled* | Whether to enable auto
configuration of the azure-eventhubs component. This is enabled by default. |
| Boolean
| *camel.component.azure-eventhubs.event-position* | Sets the map containing
the event position to use for each partition if a checkpoint for the partition
does not exist in CheckpointStore. This map is keyed off of the partition id.
If there is no checkpoint in CheckpointStore and there is no entry in this map,
the processing of the partition will start from {link EventPosition#latest()
latest} position. | | Map
| *camel.component.azure-eventhubs.lazy-start-producer* | Whether the producer
should be started lazy (on the first message). By starting lazy you can use
this to allow CamelContext and routes to startup in situations where a producer
may otherwise fail during starting and cause the route to fail being started.
By deferring this startup to be lazy then the startup failure can be handled
during routing messages via Camel's routing error handlers. Beware that when
the first message is proc [...]
| *camel.component.azure-eventhubs.partition-id* | Sets the identifier of the
Event Hub partition that the {link EventData events} will be sent to. If the
identifier is not specified, the Event Hubs service will be responsible for
routing events that are sent to an available partition. | | String
| *camel.component.azure-eventhubs.partition-key* | Sets a hashing key to be
provided for the batch of events, which instructs the Event Hubs service to map
this key to a specific partition. The selection of a partition is stable for a
given partition hashing key. Should any other batches of events be sent using
the same exact partition hashing key, the Event Hubs service will route them
all to the same partition. This should be specified only when there is a need
to group events by part [...]
| *camel.component.azure-eventhubs.prefetch-count* | Sets the count used by
the receiver to control the number of events the Event Hub consumer will
actively receive and queue locally without regard to whether a receive
operation is currently active. | 500 | Integer
-| *camel.component.azure-eventhubs.producer-async-client* | Sets the
EventHubProducerAsyncClient.An asynchronous producer responsible for
transmitting EventData to a specific Event Hub, grouped together in batches.
Depending on the {link CreateBatchOptions options} specified when creating an
\{linkEventDataBatch\}, the events may be automatically routed to an available
partition or specific to a partition. Use by this component to produce the data
in camel producer. The option is a com.a [...]
+| *camel.component.azure-eventhubs.producer-async-client* | Sets the
EventHubProducerAsyncClient.An asynchronous producer responsible for
transmitting EventData to a specific Event Hub, grouped together in batches.
Depending on the {link CreateBatchOptions options} specified when creating an
\{linkEventDataBatch}, the events may be automatically routed to an available
partition or specific to a partition. Use by this component to produce the data
in camel producer. The option is a com.az [...]
| *camel.component.azure-eventhubs.shared-access-key* | The generated value
for the SharedAccessName | | String
| *camel.component.azure-eventhubs.shared-access-name* | The name you chose
for your EventHubs SAS keys | | String
| *camel.component.azure-eventhubs.basic-property-binding* | *Deprecated*
Whether the component should use basic property binding (Camel 2.x) or the
newer property binding with additional capabilities | false | Boolean
diff --git a/docs/modules/ROOT/pages/ftp-starter.adoc
b/docs/modules/ROOT/pages/ftp-starter.adoc
index 35544d1..f422acd 100644
--- a/docs/modules/ROOT/pages/ftp-starter.adoc
+++ b/docs/modules/ROOT/pages/ftp-starter.adoc
@@ -25,14 +25,14 @@ The component supports 13 options, which are listed below.
|===
| Name | Description | Default | Type
| *camel.component.ftp.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.ftp.enabled* | Whether to enable auto configuration of the
\ftp component. This is enabled by default. | | Boolean
+| *camel.component.ftp.enabled* | Whether to enable auto configuration of the
ftp component. This is enabled by default. | | Boolean
| *camel.component.ftp.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then c [...]
| *camel.component.ftps.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.ftps.enabled* | Whether to enable auto configuration of the
\ftps component. This is enabled by default. | | Boolean
+| *camel.component.ftps.enabled* | Whether to enable auto configuration of the
ftps component. This is enabled by default. | | Boolean
| *camel.component.ftps.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then [...]
| *camel.component.ftps.use-global-ssl-context-parameters* | Enable usage of
global SSL context parameters. | false | Boolean
| *camel.component.sftp.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
-| *camel.component.sftp.enabled* | Whether to enable auto configuration of the
\sftp component. This is enabled by default. | | Boolean
+| *camel.component.sftp.enabled* | Whether to enable auto configuration of the
sftp component. This is enabled by default. | | Boolean
| *camel.component.sftp.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then [...]
| *camel.component.ftp.basic-property-binding* | *Deprecated* Whether the
component should use basic property binding (Camel 2.x) or the newer property
binding with additional capabilities | false | Boolean
| *camel.component.ftps.basic-property-binding* | *Deprecated* Whether the
component should use basic property binding (Camel 2.x) or the newer property
binding with additional capabilities | false | Boolean
diff --git a/docs/modules/ROOT/pages/grok-starter.adoc
b/docs/modules/ROOT/pages/grok-starter.adoc
index 4d46e6e..8a65d73 100644
--- a/docs/modules/ROOT/pages/grok-starter.adoc
+++ b/docs/modules/ROOT/pages/grok-starter.adoc
@@ -28,7 +28,7 @@ The component supports 6 options, which are listed below.
| *camel.dataformat.grok.content-type-header* | Whether the data format should
set the Content-Type header with the type from the data format if the data
format is capable of doing so. For example application/xml for data formats
marshalling to XML, or application/json for data formats marshalling to JSON
etc. | false | Boolean
| *camel.dataformat.grok.enabled* | Whether to enable auto configuration of
the grok data format. This is enabled by default. | | Boolean
| *camel.dataformat.grok.flattened* | Turns on flattened mode. In flattened
mode the exception is thrown when there are multiple pattern matches with same
key. | false | Boolean
-| *camel.dataformat.grok.named-only* | Whether to capture named expressions
only or not (i.e. %{IP:ip} but not \$\{IP\}) | false | Boolean
+| *camel.dataformat.grok.named-only* | Whether to capture named expressions
only or not (i.e. %{IP:ip} but not $\{IP}) | false | Boolean
| *camel.dataformat.grok.pattern* | The grok pattern to match lines of input |
| String
|===
// spring-boot-auto-configure options: END
diff --git a/docs/modules/ROOT/pages/kafka-starter.adoc
b/docs/modules/ROOT/pages/kafka-starter.adoc
index 3c6bd9a..f13910b 100644
--- a/docs/modules/ROOT/pages/kafka-starter.adoc
+++ b/docs/modules/ROOT/pages/kafka-starter.adoc
@@ -56,7 +56,7 @@ The component supports 98 options, which are listed below.
| *camel.component.kafka.kafka-manual-commit-factory* | Factory to use for
creating KafkaManualCommit instances. This allows to plugin a custom factory to
create custom KafkaManualCommit instances in case special logic is needed when
doing manual commits that deviates from the default implementation that comes
out of the box. The option is a
org.apache.camel.component.kafka.KafkaManualCommitFactory type. | | String
| *camel.component.kafka.kerberos-before-relogin-min-time* | Login thread
sleep time between refresh attempts. | 60000 | Integer
| *camel.component.kafka.kerberos-init-cmd* | Kerberos kinit command path.
Default is /usr/bin/kinit | /usr/bin/kinit | String
-| *camel.component.kafka.kerberos-principal-to-local-rules* | A list of rules
for mapping from principal names to short names (typically operating system
usernames). The rules are evaluated in order and the first rule that matches a
principal name is used to map it to a short name. Any later rules in the list
are ignored. By default, principal names of the form
\{username\}/\{hostname\}\{REALM\} are mapped to \{username\}. For more details
on the format please see the security authorizat [...]
+| *camel.component.kafka.kerberos-principal-to-local-rules* | A list of rules
for mapping from principal names to short names (typically operating system
usernames). The rules are evaluated in order and the first rule that matches a
principal name is used to map it to a short name. Any later rules in the list
are ignored. By default, principal names of the form
\{username}/\{hostname}\{REALM} are mapped to \{username}. For more details on
the format please see the security authorization [...]
| *camel.component.kafka.kerberos-renew-jitter* | Percentage of random jitter
added to the renewal time. | | Double
| *camel.component.kafka.kerberos-renew-window-factor* | Login thread will
sleep until the specified window factor of time from last refresh to ticket's
expiry has been reached, at which time it will try to renew the ticket. | |
Double
| *camel.component.kafka.key* | The record key (or null if no key is
specified). If this option has been configured then it take precedence over
header KafkaConstants#KEY | | String
