camel-google-drive-kafka-connector sink configuration

When using camel-google-drive-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-drive-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.googledrive.CamelGoogledriveSinkConnector

The camel-google-drive sink connector supports 22 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.apiName	What kind of operation to perform One of: [DRIVE_ABOUT] [DRIVE_APPS] [DRIVE_CHANGES] [DRIVE_CHANNELS] [DRIVE_CHILDREN] [DRIVE_COMMENTS] [DRIVE_FILES] [DRIVE_PARENTS] [DRIVE_PERMISSIONS] [DRIVE_PROPERTIES] [DRIVE_REALTIME] [DRIVE_REPLIES] [DRIVE_REVISIONS]	null	true	HIGH
camel.sink.path.methodName	What sub operation to use for the selected operation One of: [copy] [delete] [get] [getIdForEmail] [insert] [list] [patch] [stop] [touch] [trash] [untrash] [update] [watch]	null	true	HIGH
camel.sink.endpoint.applicationName	Google drive application name. Example would be camel-google-drive/1.0	null	false	MEDIUM
camel.sink.endpoint.clientFactory	To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory	null	false	MEDIUM
camel.sink.endpoint.clientId	Client ID of the drive application	null	false	MEDIUM
camel.sink.endpoint.inBody	Sets the name of a parameter to be passed in the exchange In Body	null	false	MEDIUM
camel.sink.endpoint.scopes	Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.	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.synchronous	Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).	false	false	MEDIUM
camel.sink.endpoint.accessToken	OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.	null	false	MEDIUM
camel.sink.endpoint.clientSecret	Client secret of the drive application	null	false	MEDIUM
camel.sink.endpoint.refreshToken	OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.	null	false	MEDIUM
camel.component.google-drive.applicationName	Google drive application name. Example would be camel-google-drive/1.0	null	false	MEDIUM
camel.component.google-drive.clientId	Client ID of the drive application	null	false	MEDIUM
camel.component.google-drive.configuration	To use the shared configuration	null	false	MEDIUM
camel.component.google-drive.scopes	Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.	null	false	MEDIUM
camel.component.google-drive.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-drive.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-drive.clientFactory	To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory	null	false	MEDIUM
camel.component.google-drive.accessToken	OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.	null	false	MEDIUM
camel.component.google-drive.clientSecret	Client secret of the drive application	null	false	MEDIUM
camel.component.google-drive.refreshToken	OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.	null	false	MEDIUM

Name

Description

Default

Required

Priority

camel.sink.path.apiName

What kind of operation to perform One of: [DRIVE_ABOUT] [DRIVE_APPS] [DRIVE_CHANGES] [DRIVE_CHANNELS] [DRIVE_CHILDREN] [DRIVE_COMMENTS] [DRIVE_FILES] [DRIVE_PARENTS] [DRIVE_PERMISSIONS] [DRIVE_PROPERTIES] [DRIVE_REALTIME] [DRIVE_REPLIES] [DRIVE_REVISIONS]

null

true

HIGH

camel.sink.path.methodName

What sub operation to use for the selected operation One of: [copy] [delete] [get] [getIdForEmail] [insert] [list] [patch] [stop] [touch] [trash] [untrash] [update] [watch]

null

true

HIGH

camel.sink.endpoint.applicationName

Google drive application name. Example would be camel-google-drive/1.0

null

false

MEDIUM

camel.sink.endpoint.clientFactory

To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory

null

false

MEDIUM

camel.sink.endpoint.clientId

Client ID of the drive application

null

false

MEDIUM

camel.sink.endpoint.inBody

Sets the name of a parameter to be passed in the exchange In Body

null

false

MEDIUM

camel.sink.endpoint.scopes

Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.

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.synchronous

Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).

false

MEDIUM

camel.sink.endpoint.accessToken

OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.

null

false

MEDIUM

camel.sink.endpoint.clientSecret

Client secret of the drive application

null

false

MEDIUM

camel.sink.endpoint.refreshToken

OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.

null

false

MEDIUM

camel.component.google-drive.applicationName

Google drive application name. Example would be camel-google-drive/1.0

null

false

MEDIUM

camel.component.google-drive.clientId

Client ID of the drive application

null

false

MEDIUM

camel.component.google-drive.configuration

To use the shared configuration

null

false

MEDIUM

camel.component.google-drive.scopes

Specifies the level of permissions you want a drive application to have to a user account. See https://developers.google.com/drive/web/scopes for more info.

null

false

MEDIUM

camel.component.google-drive.lazyStartProducer

false

MEDIUM

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

To use the GoogleCalendarClientFactory as factory for creating the client. Will by default use BatchGoogleDriveClientFactory

null

false

MEDIUM

camel.component.google-drive.accessToken

OAuth 2 access token. This typically expires after an hour so refreshToken is recommended for long term usage.

null

false

MEDIUM

camel.component.google-drive.clientSecret

Client secret of the drive application

null

false

MEDIUM

camel.component.google-drive.refreshToken

OAuth 2 refresh token. Using this, the Google Calendar component can obtain a new accessToken whenever the current one expires - a necessity if the application is long-lived.

null

false

MEDIUM

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

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

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