camel-atmos-kafka-connector source configuration

Connector description: Integrate with EMC’s ViPR object data services using the Atmos Client.

When using camel-atmos-kafka-connector as source 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 Source connector in Kafka connect you’ll need to set the following connector.class

connector.class=org.apache.camel.kafkaconnector.atmos.CamelAtmosSourceConnector

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

Name Description Default Required Priority

camel.source.path.name

Atmos name

null

false

MEDIUM

camel.source.path.operation

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

null

true

HIGH

camel.source.endpoint.localPath

Local path to put files

null

false

MEDIUM

camel.source.endpoint.newRemotePath

New path on Atmos when moving files

null

false

MEDIUM

camel.source.endpoint.query

Search query on Atmos

null

false

MEDIUM

camel.source.endpoint.remotePath

Where to put files on Atmos

null

false

MEDIUM

camel.source.endpoint.bridgeErrorHandler

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

false

false

MEDIUM

camel.source.endpoint.exceptionHandler

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.

null

false

MEDIUM

camel.source.endpoint.exchangePattern

Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut]

null

false

MEDIUM

camel.source.endpoint.uri

Atomos server uri

null

false

MEDIUM

camel.source.endpoint.fullTokenId

Atmos client fullTokenId

null

false

MEDIUM

camel.source.endpoint.secretKey

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

null

false

MEDIUM

camel.source.endpoint.sslValidation

Atmos SSL validation

false

false

MEDIUM

camel.component.atmos.bridgeErrorHandler

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

false

false

MEDIUM

camel.component.atmos.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.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 source connector has no converters out of the box.

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

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

Back to top