camel-azure-storage-queue-kafka-connector sink configuration
When using camel-azure-storage-queue-kafka-connector as sink 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 Sink connector in Kafka connect you’ll need to set the following connector.class
connector.class=org.apache.camel.kafkaconnector.azurestoragequeue.CamelAzurestoragequeueSinkConnectorThe camel-azure-storage-queue sink connector supports 24 options, which are listed below.
| Name | Description | Default | Priority |
|---|---|---|---|
camel.sink.path.accountName |
Azure account name to be used for authentication with azure queue services |
null |
MEDIUM |
camel.sink.path.queueName |
The queue resource name |
null |
MEDIUM |
camel.sink.endpoint.serviceClient |
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. |
null |
MEDIUM |
camel.sink.endpoint.lazyStartProducer |
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 creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
MEDIUM |
camel.sink.endpoint.operation |
Queue service operation hint to the producer One of: [listQueues] [createQueue] [deleteQueue] [clearQueue] [sendMessage] [deleteMessage] [receiveMessages] [peekMessages] [updateMessage] |
null |
MEDIUM |
camel.sink.endpoint.basicPropertyBinding |
Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.sink.endpoint.synchronous |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
MEDIUM |
camel.sink.endpoint.maxMessages |
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 |
camel.sink.endpoint.timeout |
An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. |
null |
MEDIUM |
camel.sink.endpoint.timeToLive |
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. |
null |
MEDIUM |
camel.sink.endpoint.visibilityTimeout |
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. |
null |
MEDIUM |
camel.sink.endpoint.accessKey |
Access key for the associated azure account name to be used for authentication with azure queue services |
null |
MEDIUM |
camel.sink.endpoint.credentials |
StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information |
null |
MEDIUM |
camel.component.azure-storage-queue.configuration |
The component configurations |
null |
MEDIUM |
camel.component.azure-storage-queue.serviceClient |
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. |
null |
MEDIUM |
camel.component.azure-storage-queue.lazyStart 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 creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
MEDIUM |
camel.component.azure-storage-queue.operation |
Queue service operation hint to the producer One of: [listQueues] [createQueue] [deleteQueue] [clearQueue] [sendMessage] [deleteMessage] [receiveMessages] [peekMessages] [updateMessage] |
null |
MEDIUM |
camel.component.azure-storage-queue.basicProperty Binding |
Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities |
false |
MEDIUM |
camel.component.azure-storage-queue.maxMessages |
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 |
camel.component.azure-storage-queue.timeout |
An optional timeout applied to the operation. If a response is not returned before the timeout concludes a RuntimeException will be thrown. |
null |
MEDIUM |
camel.component.azure-storage-queue.timeToLive |
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. |
null |
MEDIUM |
camel.component.azure-storage-queue.visibility Timeout |
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. |
null |
MEDIUM |
camel.component.azure-storage-queue.accessKey |
Access key for the associated azure account name to be used for authentication with azure queue services |
null |
MEDIUM |
camel.component.azure-storage-queue.credentials |
StorageSharedKeyCredential can be injected to create the azure client, this holds the important authentication information |
null |
MEDIUM |