camel-influxdb-kafka-connector sink configuration

When using camel-influxdb-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-influxdb-kafka-connector</artifactId>
  <version>x.x.x</version>
  <!-- use the same version as your Camel Kafka connector version -->
</dependency>

The camel-influxdb sink connector supports 12 options, which are listed below.

Name Description Default Priority

camel.sink.path.connectionBean

Connection to the influx database, of class InfluxDB.class

null

HIGH

camel.sink.endpoint.batch

Define if this operation is a batch operation or not

false

MEDIUM

camel.sink.endpoint.databaseName

The name of the database where the time series will be stored

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

Define if this operation is an insert or a query

"insert"

MEDIUM

camel.sink.endpoint.query

Define the query in case of operation query

null

MEDIUM

camel.sink.endpoint.retentionPolicy

The string that defines the retention policy to the data created by the endpoint

"default"

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.component.influxdb.influxDB

The shared Influx DB to use for all endpoints

null

MEDIUM

camel.component.influxdb.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.component.influxdb.basicPropertyBinding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

MEDIUM