camel-telegram-kafka-connector sink configuration

When using camel-telegram-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-telegram-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.telegram.CamelTelegramSinkConnector

The camel-telegram sink connector supports 17 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.type	The endpoint type. Currently, only the 'bots' type is supported. One of: [bots]	null	true	HIGH
camel.sink.endpoint.chatId	The identifier of the chat that will receive the produced messages. Chat ids can be first obtained from incoming messages (eg. when a telegram user starts a conversation with a bot, its client sends automatically a '/start' message containing the chat id). It is an optional parameter, as the chat id can be set dynamically for each outgoing message (using body or headers).	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.baseUri	Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API	null	false	MEDIUM
camel.sink.endpoint.bufferSize	The initial in-memory buffer size used when transferring data between Camel and AHC Client.	4096	false	MEDIUM
camel.sink.endpoint.clientConfig	To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.	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.sink.endpoint.proxyHost	HTTP proxy host which could be used when sending out the message.	null	false	MEDIUM
camel.sink.endpoint.proxyPort	HTTP proxy port which could be used when sending out the message.	null	false	MEDIUM
camel.sink.endpoint.proxyType	HTTP proxy type which could be used when sending out the message. One of: [HTTP] [SOCKS4] [SOCKS5]	"HTTP"	false	MEDIUM
camel.sink.endpoint.authorizationToken	The authorization token for using the bot (ask the BotFather)	null	true	HIGH
camel.component.telegram.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.telegram.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.telegram.baseUri	Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API	"https://api.telegram.org"	false	MEDIUM
camel.component.telegram.client	To use a custom AsyncHttpClient	null	false	MEDIUM
camel.component.telegram.clientConfig	To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.	null	false	MEDIUM
camel.component.telegram.authorizationToken	The default Telegram authorization token to be used when the information is not provided in the endpoints.	null	false	MEDIUM

Name

Description

Default

Required

Priority

camel.sink.path.type

The endpoint type. Currently, only the 'bots' type is supported. One of: [bots]

null

true

HIGH

camel.sink.endpoint.chatId

The identifier of the chat that will receive the produced messages. Chat ids can be first obtained from incoming messages (eg. when a telegram user starts a conversation with a bot, its client sends automatically a '/start' message containing the chat id). It is an optional parameter, as the chat id can be set dynamically for each outgoing message (using body or headers).

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

Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API

null

false

MEDIUM

camel.sink.endpoint.bufferSize

The initial in-memory buffer size used when transferring data between Camel and AHC Client.

4096

false

MEDIUM

camel.sink.endpoint.clientConfig

To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.

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.sink.endpoint.proxyHost

HTTP proxy host which could be used when sending out the message.

null

false

MEDIUM

camel.sink.endpoint.proxyPort

HTTP proxy port which could be used when sending out the message.

null

false

MEDIUM

camel.sink.endpoint.proxyType

HTTP proxy type which could be used when sending out the message. One of: [HTTP] [SOCKS4] [SOCKS5]

"HTTP"

false

MEDIUM

camel.sink.endpoint.authorizationToken

The authorization token for using the bot (ask the BotFather)

null

true

HIGH

camel.component.telegram.lazyStartProducer

false

MEDIUM

camel.component.telegram.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.telegram.baseUri

Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API

"https://api.telegram.org"

false

MEDIUM

camel.component.telegram.client

To use a custom AsyncHttpClient

null

false

MEDIUM

camel.component.telegram.clientConfig

To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.

null

false

MEDIUM

camel.component.telegram.authorizationToken

The default Telegram authorization token to be used when the information is not provided in the endpoints.

null

false

MEDIUM

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

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

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