camel-avro-kafka-connector sink configuration

When using camel-avro-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-avro-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.avro.CamelAvroSinkConnector

The camel-avro sink connector supports 21 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.transport	Transport to use, can be either http or netty One of: [http] [netty]	null	true	HIGH
camel.sink.path.port	Port number to use	null	true	HIGH
camel.sink.path.host	Hostname to use	null	true	HIGH
camel.sink.path.messageName	The name of the message to send.	null	false	MEDIUM
camel.sink.endpoint.protocol	Avro protocol to use	null	false	MEDIUM
camel.sink.endpoint.protocolClassName	Avro protocol to use defined by the FQN class name	null	false	MEDIUM
camel.sink.endpoint.protocolLocation	Avro protocol location	null	false	MEDIUM
camel.sink.endpoint.reflectionProtocol	If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected	false	false	MEDIUM
camel.sink.endpoint.singleParameter	If true, consumer parameter won’t be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message	false	false	MEDIUM
camel.sink.endpoint.uriAuthority	Authority to use (username and password)	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.synchronous	Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).	false	false	MEDIUM
camel.component.avro.protocol	Avro protocol to use	null	false	MEDIUM
camel.component.avro.protocolClassName	Avro protocol to use defined by the FQN class name	null	false	MEDIUM
camel.component.avro.protocolLocation	Avro protocol location	null	false	MEDIUM
camel.component.avro.reflectionProtocol	If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected	false	false	MEDIUM
camel.component.avro.singleParameter	If true, consumer parameter won’t be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message	false	false	MEDIUM
camel.component.avro.uriAuthority	Authority to use (username and password)	null	false	MEDIUM
camel.component.avro.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.avro.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
camel.component.avro.configuration	To use a shared AvroConfiguration to configure options once	null	false	MEDIUM

Name

Description

Default

Required

Priority

camel.sink.path.transport

Transport to use, can be either http or netty One of: [http] [netty]

null

true

HIGH

camel.sink.path.port

Port number to use

null

true

HIGH

camel.sink.path.host

Hostname to use

null

true

HIGH

camel.sink.path.messageName

The name of the message to send.

null

false

MEDIUM

camel.sink.endpoint.protocol

Avro protocol to use

null

false

MEDIUM

camel.sink.endpoint.protocolClassName

Avro protocol to use defined by the FQN class name

null

false

MEDIUM

camel.sink.endpoint.protocolLocation

Avro protocol location

null

false

MEDIUM

camel.sink.endpoint.reflectionProtocol

If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected

false

MEDIUM

camel.sink.endpoint.singleParameter

If true, consumer parameter won’t be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message

false

MEDIUM

camel.sink.endpoint.uriAuthority

Authority to use (username and password)

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

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

MEDIUM

camel.component.avro.protocol

Avro protocol to use

null

false

MEDIUM

camel.component.avro.protocolClassName

Avro protocol to use defined by the FQN class name

null

false

MEDIUM

camel.component.avro.protocolLocation

Avro protocol location

null

false

MEDIUM

camel.component.avro.reflectionProtocol

If protocol object provided is reflection protocol. Should be used only with protocol parameter because for protocolClassName protocol type will be auto detected

false

MEDIUM

camel.component.avro.singleParameter

If true, consumer parameter won’t be wrapped into array. Will fail if protocol specifies more then 1 parameter for the message

false

MEDIUM

camel.component.avro.uriAuthority

Authority to use (username and password)

null

false

MEDIUM

camel.component.avro.lazyStartProducer

false

MEDIUM

camel.component.avro.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

camel.component.avro.configuration

To use a shared AvroConfiguration to configure options once

null

false

MEDIUM

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

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

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