blob: d3f24079f5e135136a277ae5f84f773744af0c47 [file] [log] [blame]
// kafka-connector options: START
[[camel-google-bigquery-kafka-connector-sink]]
= 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:
[source,xml]
----
<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>
----
The camel-google-bigquery sink connector supports 13 options, which are listed below.
[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Priority
| *camel.sink.path.projectId* | Google Cloud Project Id | null | ConfigDef.Importance.HIGH
| *camel.sink.path.datasetId* | BigQuery Dataset Id | null | ConfigDef.Importance.HIGH
| *camel.sink.path.tableId* | BigQuery table id | null | ConfigDef.Importance.MEDIUM
| *camel.sink.endpoint.connection Factory* | ConnectionFactory to obtain connection to Bigquery Service. If non provided the default one will be used | null | ConfigDef.Importance.MEDIUM
| *camel.sink.endpoint.lazyStart Producer* | 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 | ConfigDef.Importance.MEDIUM
| *camel.sink.endpoint.useAs InsertId* | Field name to use as insert id | null | ConfigDef.Importance.MEDIUM
| *camel.sink.endpoint.basic PropertyBinding* | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
| * camel.sink.endpoint.synchronous* | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | ConfigDef.Importance.MEDIUM
| * camel.component.google-bigquery.connection Factory* | ConnectionFactory to obtain connection to Bigquery Service. If non provided the default one will be used | null | ConfigDef.Importance.MEDIUM
| * camel.component.google-bigquery.dataset Id* | BigQuery Dataset Id | null | ConfigDef.Importance.MEDIUM
| * camel.component.google-bigquery.lazy StartProducer* | 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 | ConfigDef.Importance.MEDIUM
| * camel.component.google-bigquery.project Id* | Google Cloud Project Id | null | ConfigDef.Importance.MEDIUM
| * camel.component.google-bigquery.basic PropertyBinding* | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | ConfigDef.Importance.MEDIUM
|===
// kafka-connector options: END