camel-google-pubsub-kafka-connector source configuration
When using camel-google-pubsub-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-google-pubsub-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.googlepubsub.CamelGooglepubsubSourceConnector
The camel-google-pubsub source connector supports 15 options, which are listed below.
Name | Description | Default | Required | Priority |
---|---|---|---|---|
camel.source.path.projectId |
Project Id |
null |
true |
HIGH |
camel.source.path.destinationName |
Destination Name |
null |
true |
HIGH |
camel.source.endpoint.ackMode |
AUTO = exchange gets ack’ed/nack’ed on completion. NONE = downstream process has to ack/nack explicitly One of: [AUTO] [NONE] |
"AUTO" |
false |
MEDIUM |
camel.source.endpoint.concurrentConsumers |
The number of parallel streams consuming from the subscription |
"1" |
false |
MEDIUM |
camel.source.endpoint.loggerId |
Logger ID to use when a match to the parent route required |
null |
false |
MEDIUM |
camel.source.endpoint.maxMessagesPerPoll |
The max number of messages to receive from the server in a single API call |
"1" |
false |
MEDIUM |
camel.source.endpoint.synchronousPull |
Synchronously pull batches of messages |
false |
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.synchronous |
Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). |
false |
false |
MEDIUM |
camel.component.google-pubsub.endpoint |
Endpoint to use with local Pub/Sub emulator. |
null |
false |
MEDIUM |
camel.component.google-pubsub.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.google-pubsub.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.google-pubsub.publisherTermination Timeout |
How many milliseconds should a producer be allowed to terminate. |
null |
false |
MEDIUM |
The camel-google-pubsub source connector has no converters out of the box.
The camel-google-pubsub source connector has no transforms out of the box.
The camel-google-pubsub source connector has no aggregation strategies out of the box.