camel-ironmq-kafka-connector sink configuration

When using camel-ironmq-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-ironmq-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.ironmq.CamelIronmqSinkConnector

The camel-ironmq sink connector supports 11 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.queueName	The name of the IronMQ queue	null	true	HIGH
camel.sink.endpoint.client	Reference to a io.iron.ironmq.Client in the Registry.	null	false	MEDIUM
camel.sink.endpoint.ironMQCloud	IronMq Cloud url. Urls for public clusters: https://mq-aws-us-east-1-1.iron.io (US) and https://mq-aws-eu-west-1-1.iron.io (EU)	"https://mq-aws-us-east-1-1.iron.io"	false	MEDIUM
camel.sink.endpoint.preserveHeaders	Should message headers be preserved when publishing messages. This will add the Camel headers to the Iron MQ message as a json payload with a header list, and a message body. Useful when Camel is both consumer and producer.	false	false	MEDIUM
camel.sink.endpoint.projectId	IronMQ projectId	null	false	MEDIUM
camel.sink.endpoint.token	IronMQ token	null	false	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	false	MEDIUM
camel.sink.endpoint.visibilityDelay	The item will not be available on the queue until this many seconds have passed. Default is 0 seconds.	null	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	false	MEDIUM
camel.component.ironmq.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	false	MEDIUM
camel.component.ironmq.autowiredEnabled	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	false	MEDIUM

Name

Description

Default

Required

Priority

camel.sink.path.queueName

The name of the IronMQ queue

null

true

HIGH

camel.sink.endpoint.client

Reference to a io.iron.ironmq.Client in the Registry.

null

false

MEDIUM

camel.sink.endpoint.ironMQCloud

IronMq Cloud url. Urls for public clusters: https://mq-aws-us-east-1-1.iron.io (US) and https://mq-aws-eu-west-1-1.iron.io (EU)

"https://mq-aws-us-east-1-1.iron.io"

false

MEDIUM

camel.sink.endpoint.preserveHeaders

Should message headers be preserved when publishing messages. This will add the Camel headers to the Iron MQ message as a json payload with a header list, and a message body. Useful when Camel is both consumer and producer.

false

MEDIUM

camel.sink.endpoint.projectId

IronMQ projectId

null

false

MEDIUM

camel.sink.endpoint.token

IronMQ token

null

false

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.visibilityDelay

The item will not be available on the queue until this many seconds have passed. Default is 0 seconds.

null

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.component.ironmq.lazyStartProducer

false

MEDIUM

camel.component.ironmq.autowiredEnabled

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

false

MEDIUM

The camel-ironmq sink connector has no converters out of the box.

The camel-ironmq sink connector has no transforms out of the box.

The camel-ironmq sink connector has no aggregation strategies out of the box.