camel-google-storage-kafka-connector sink configuration
Connector Description: Store and retrieve objects from Google Cloud Storage Service using the google-cloud-storage library.
When using camel-google-storage-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-storage-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.googlestorage.CamelGooglestorageSinkConnector
The camel-google-storage sink connector supports 19 options, which are listed below.
Name | Description | Default | Priority |
---|---|---|---|
Required Bucket name or ARN. |
HIGH |
||
Setting the autocreation of the bucket bucketName. |
true |
MEDIUM |
|
The Service account key that can be used as credentials for the Storage client. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. |
MEDIUM |
||
The Cloud Storage class to use when creating the new buckets. |
"STANDARD" |
MEDIUM |
|
The storage client. |
MEDIUM |
||
The Cloud Storage location to use when creating the new buckets. |
"US-EAST1" |
MEDIUM |
|
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 |
|
The Object name inside the bucket. |
MEDIUM |
||
Set the operation for the producer One of: [copyObject] [listObjects] [deleteObject] [deleteBucket] [listBuckets] [getObject] [createDownloadLink]. Enum values:
|
MEDIUM |
||
Setting the autocreation of the bucket bucketName. |
true |
MEDIUM |
|
The component configuration. |
MEDIUM |
||
The Service account key that can be used as credentials for the Storage client. It can be loaded by default from classpath, but you can prefix with classpath:, file:, or http: to load the resource from different systems. |
MEDIUM |
||
The Cloud Storage class to use when creating the new buckets. |
"STANDARD" |
MEDIUM |
|
The storage client. |
MEDIUM |
||
The Cloud Storage location to use when creating the new buckets. |
"US-EAST1" |
MEDIUM |
|
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 |
|
The Object name inside the bucket. |
MEDIUM |
||
Set the operation for the producer One of: [copyObject] [listObjects] [deleteObject] [deleteBucket] [listBuckets] [getObject] [createDownloadLink]. Enum values:
|
MEDIUM |
||
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 |
MEDIUM |
The camel-google-storage sink connector has no converters out of the box.
The camel-google-storage sink connector has no transforms out of the box.
The camel-google-storage sink connector has no aggregation strategies out of the box.