camel-google-pubsub-kafka-connector sink configuration

When using camel-google-pubsub-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-google-pubsub-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.googlepubsub.CamelGooglepubsubSinkConnector

The camel-google-pubsub sink connector supports 16 options, which are listed below.

Name Description Default Priority

camel.sink.path.projectId

Project Id

null

HIGH

camel.sink.path.destinationName

Destination Name

null

HIGH

camel.sink.endpoint.ackMode

AUTO = exchange gets ack’ed/nack’ed on completion. NONE = downstream process has to ack/nack explicitly One of: [AUTO] [NONE]

"AUTO"

MEDIUM

camel.sink.endpoint.concurrentConsumers

The number of parallel streams consuming from the subscription

"1"

MEDIUM

camel.sink.endpoint.loggerId

Logger ID to use when a match to the parent route required

null

MEDIUM

camel.sink.endpoint.maxMessagesPerPoll

The max number of messages to receive from the server in a single API call

"1"

MEDIUM

camel.sink.endpoint.synchronousPull

Synchronously pull batches of messages

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.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.google-pubsub.endpoint

Endpoint to use with local Pub/Sub emulator.

null

MEDIUM

camel.component.google-pubsub.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.google-pubsub.publisherCacheSize

Maximum number of producers to cache. This could be increased if you have producers for lots of different topics.

null

MEDIUM

camel.component.google-pubsub.publisherCache Timeout

How many milliseconds should each producer stay alive in the cache.

null

MEDIUM

camel.component.google-pubsub.basicPropertyBinding

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

false

MEDIUM

camel.component.google-pubsub.publisherTermination Timeout

How many milliseconds should a producer be allowed to terminate.

null

MEDIUM

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

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

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