camel-google-bigquery-kafka-connector sink configuration

When using camel-google-bigquery-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-bigquery-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.googlebigquery.CamelGooglebigquerySinkConnector

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

Name	Description	Default	Required	Priority
camel.sink.path.projectId	Google Cloud Project Id	null	true	HIGH
camel.sink.path.datasetId	BigQuery Dataset Id	null	true	HIGH
camel.sink.path.tableId	BigQuery table id	null	false	MEDIUM
camel.sink.endpoint.connectionFactory	ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used	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.useAsInsertId	Field name to use as insert id	null	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.component.google-bigquery.connectionFactory	ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used	null	false	MEDIUM
camel.component.google-bigquery.datasetId	BigQuery Dataset Id	null	false	MEDIUM
camel.component.google-bigquery.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.google-bigquery.projectId	Google Cloud Project Id	null	false	MEDIUM
camel.component.google-bigquery.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

Name

Description

Default

Required

Priority

camel.sink.path.projectId

Google Cloud Project Id

null

true

HIGH

camel.sink.path.datasetId

BigQuery Dataset Id

null

true

HIGH

camel.sink.path.tableId

BigQuery table id

null

false

MEDIUM

camel.sink.endpoint.connectionFactory

ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used

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

MEDIUM

camel.sink.endpoint.useAsInsertId

Field name to use as insert id

null

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-bigquery.connectionFactory

ConnectionFactory to obtain connection to Bigquery Service. If not provided the default one will be used

null

false

MEDIUM

camel.component.google-bigquery.datasetId

BigQuery Dataset Id

null

false

MEDIUM

camel.component.google-bigquery.lazyStartProducer

false

MEDIUM

camel.component.google-bigquery.projectId

Google Cloud Project Id

null

false

MEDIUM

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

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

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

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