camel-azure-storage-queue-kafka-connector source configuration
Connector Description: The azure-storage-queue component is used for storing and retrieving the messages to/from Azure Storage Queue using Azure SDK v12.
When using camel-azure-storage-queue-kafka-connector as source make sure to use the following Maven dependency to have support for the connector:
<dependency>
<groupId>org.apache.camel.kafkaconnector</groupId>
<artifactId>camel-azure-storage-queue-kafka-connector</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel Kafka connector version -->
</dependency>
To use this source connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.azurestoragequeue.CamelAzurestoragequeueSourceConnector
The camel-azure-storage-queue source connector supports 42 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Azure account name to be used for authentication with azure queue services. |
MEDIUM |
||
The queue resource name. |
MEDIUM |
||
Service client to a storage account to interact with the queue service. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. This client contains all the operations for interacting with a queue account in Azure Storage. Operations allowed by the client are creating, listing, and deleting queues, retrieving and updating properties of the account, and retrieving statistics of the account. |
MEDIUM |
||
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 |
MEDIUM |
|
If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. |
false |
MEDIUM |
|
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
MEDIUM |
||
Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]. Enum values:
|
MEDIUM |
||
A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. |
MEDIUM |
||
Maximum number of messages to get, if there are less messages exist in the queue than requested all the messages will be returned. If left empty only 1 message will be retrieved, the allowed range is 1 to 32 messages. |
"1" |
MEDIUM |
|
The ID of the message to be deleted or updated. |
MEDIUM |
||
Unique identifier that must match for the message to be deleted or updated. |
MEDIUM |
||
An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. |
MEDIUM |
||
How long the message will stay alive in the queue. If unset the value will default to 7 days, if -1 is passed the message will not expire. The time to live must be -1 or any positive number. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S — parses as 20.345 seconds, P2D — parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe. |
MEDIUM |
||
The timeout period for how long the message is invisible in the queue. The timeout must be between 1 seconds and 7 days. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S — parses as 20.345 seconds, P2D — parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe. |
MEDIUM |
||
The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. |
MEDIUM |
||
The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. |
MEDIUM |
||
To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. |
MEDIUM |
||
Milliseconds before the next poll. |
500L |
MEDIUM |
|
If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. |
false |
MEDIUM |
|
Milliseconds before the first poll starts. |
1000L |
MEDIUM |
|
Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. |
0L |
MEDIUM |
|
The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF]. Enum values:
|
"TRACE" |
MEDIUM |
|
Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. |
MEDIUM |
||
To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler. |
"none" |
MEDIUM |
|
To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. |
MEDIUM |
||
Whether the scheduler should be auto started. |
true |
MEDIUM |
|
Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS]. Enum values:
|
"MILLISECONDS" |
MEDIUM |
|
Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. |
true |
MEDIUM |
|
Access key for the associated azure account name to be used for authentication with azure queue services. |
MEDIUM |
||
StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information. |
MEDIUM |
||
The component configurations. |
MEDIUM |
||
Service client to a storage account to interact with the queue service. This client does not hold any state about a particular storage account but is instead a convenient way of sending off appropriate requests to the resource on the service. This client contains all the operations for interacting with a queue account in Azure Storage. Operations allowed by the client are creating, listing, and deleting queues, retrieving and updating properties of the account, and retrieving statistics of the account. |
MEDIUM |
||
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 |
MEDIUM |
|
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
MEDIUM |
|
Maximum number of messages to get, if there are less messages exist in the queue than requested all the messages will be returned. If left empty only 1 message will be retrieved, the allowed range is 1 to 32 messages. |
"1" |
MEDIUM |
|
The ID of the message to be deleted or updated. |
MEDIUM |
||
Unique identifier that must match for the message to be deleted or updated. |
MEDIUM |
||
An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. |
MEDIUM |
||
How long the message will stay alive in the queue. If unset the value will default to 7 days, if -1 is passed the message will not expire. The time to live must be -1 or any positive number. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S — parses as 20.345 seconds, P2D — parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe. |
MEDIUM |
||
The timeout period for how long the message is invisible in the queue. The timeout must be between 1 seconds and 7 days. The format should be in this form: PnDTnHnMn.nS., e.g: PT20.345S — parses as 20.345 seconds, P2D — parses as 2 days However, in case you are using EndpointDsl/ComponentDsl, you can do something like Duration.ofSeconds() since these Java APIs are typesafe. |
MEDIUM |
||
Access key for the associated azure account name to be used for authentication with azure queue services. |
MEDIUM |
||
StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information. |
MEDIUM |
The camel-azure-storage-queue source connector has no converters out of the box.
The camel-azure-storage-queue source connector has no transforms out of the box.
The camel-azure-storage-queue source connector has no aggregation strategies out of the box.