camel-thrift-kafka-connector sink configuration

When using camel-thrift-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-thrift-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.thrift.CamelThriftSinkConnector

The camel-thrift sink connector supports 13 options, which are listed below.

Name Description Default Required Priority

camel.sink.path.host

The Thrift server host name. This is localhost or 0.0.0.0 (if not defined) when being a consumer or remote server host name when using producer.

null

false

MEDIUM

camel.sink.path.port

The Thrift server port

null

true

HIGH

camel.sink.path.service

Fully qualified service name from the thrift descriptor file (package dot service definition name)

null

true

HIGH

camel.sink.endpoint.compressionType

Protocol compression mechanism type One of: [NONE] [ZLIB]

"NONE"

false

MEDIUM

camel.sink.endpoint.exchangeProtocol

Exchange protocol serialization type One of: [BINARY] [JSON] [SJSON] [COMPACT]

"BINARY"

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

The Thrift invoked method name

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.sink.endpoint.negotiationType

Security negotiation type One of: [PLAINTEXT] [SSL] [SASL]

"PLAINTEXT"

false

MEDIUM

camel.sink.endpoint.sslParameters

Configuration parameters for SSL/TLS security negotiation

null

false

MEDIUM

camel.component.thrift.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.thrift.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.thrift.useGlobalSslContext Parameters

Determine if the thrift component is using global SSL context parameters

false

false

MEDIUM

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

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

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

Back to top