camel-atmos-kafka-connector sink configuration

When using camel-atmos-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-atmos-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.atmos.CamelAtmosSinkConnector

The camel-atmos sink connector supports 19 options, which are listed below.

Name Description Default Required Priority

camel.sink.path.name

Atmos name

null

false

MEDIUM

camel.sink.path.operation

Operation to perform One of: [put] [del] [search] [get] [move]

null

true

HIGH

camel.sink.endpoint.localPath

Local path to put files

null

false

MEDIUM

camel.sink.endpoint.newRemotePath

New path on Atmos when moving files

null

false

MEDIUM

camel.sink.endpoint.query

Search query on Atmos

null

false

MEDIUM

camel.sink.endpoint.remotePath

Where to put files on Atmos

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

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

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

Atomos server uri

null

false

MEDIUM

camel.sink.endpoint.fullTokenId

Atmos client fullTokenId

null

false

MEDIUM

camel.sink.endpoint.secretKey

The secret key to pass to the Atmos client (should be base64 encoded)

null

false

MEDIUM

camel.sink.endpoint.sslValidation

Atmos SSL validation

false

false

MEDIUM

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

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

false

false

LOW

camel.component.atmos.uri

The URI of the server for the Atmos client to connect to

null

false

MEDIUM

camel.component.atmos.fullTokenId

The token id to pass to the Atmos client

null

false

MEDIUM

camel.component.atmos.secretKey

The secret key to pass to the Atmos client (should be base64 encoded)

null

false

MEDIUM

camel.component.atmos.sslValidation

Whether the Atmos client should perform SSL validation

false

false

MEDIUM

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

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

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

Back to top