camel-azure-storage-datalake-kafka-connector source configuration

name of the azure account.

name of filesystem to be used.

account key for authentication.

client id for azure account.

client secret for azure account.

client secret credential for authentication.

Whether or not a file changed event raised indicates completion (true) or modification (false).

check for closing stream after read.

count number of bytes to download.

service client of datalake.

directory of the file to be handled in component.

download link expiration time.

expression for queryInputStream.

directory of file to do operations in the local system.

name of file to be handled in component.

offset position in file for different operations.

maximum number of results to show at a time.

no of retries to a given request.

set open options for creating file.

path in azure datalake for operations.

permission string for the file.

This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file.

recursively include all paths.

regular expression for matching file names.

Whether or not uncommitted data is to be retained after the operation.

datalake service client for azure storage datalake.

shared key credential for azure datalake gen2.

tenant id for azure account.

Timeout for operation.

umask permission for file.

whether or not to use upn.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.

To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.

Sets the exchange pattern when the consumer creates an exchange. One of: [InOnly] [InOut] [InOptionalOut].

Enum values:

A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.

The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.

The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.

To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.

Milliseconds before the next poll.

If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.

Milliseconds before the first poll starts.

Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.

The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. One of: [TRACE] [DEBUG] [INFO] [WARN] [ERROR] [OFF].

Enum values:

Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.

To use a cron scheduler from either camel-spring or camel-quartz component. Use value spring or quartz for built in scheduler.

To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.

Whether the scheduler should be auto started.

Time unit for initialDelay and delay options. One of: [NANOSECONDS] [MICROSECONDS] [MILLISECONDS] [SECONDS] [MINUTES] [HOURS] [DAYS].

Enum values:

Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.

account key for authentication.

client id for azure account.

client secret for azure account.

client secret credential for authentication.

Whether or not a file changed event raised indicates completion (true) or modification (false).

check for closing stream after read.

configuration object for datalake.

count number of bytes to download.

directory of the file to be handled in component.

download link expiration time.

expression for queryInputStream.

directory of file to do operations in the local system.

name of file to be handled in component.

offset position in file for different operations.

maximum number of results to show at a time.

no of retries to a given request.

set open options for creating file.

path in azure datalake for operations.

permission string for the file.

This parameter allows the caller to upload data in parallel and control the order in which it is appended to the file.

recursively include all paths.

regular expression for matching file names.

Whether or not uncommitted data is to be retained after the operation.

datalake service client for azure storage datalake.

shared key credential for azure datalake gen2.

tenant id for azure account.

Timeout for operation.

umask permission for file.

whether or not to use upn.

Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

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.