camel-weka-kafka-connector sink configuration

When using camel-weka-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-weka-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.weka.CamelWekaSinkConnector

The camel-weka sink connector supports 14 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.command	The command to use. One of: [filter] [model] [read] [write] [push] [pop] [version]	null	true	HIGH
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.apply	The filter spec (i.e. Name Options)	null	false	MEDIUM
camel.sink.endpoint.build	The classifier spec (i.e. Name Options)	null	false	MEDIUM
camel.sink.endpoint.dsname	The named dataset to train the classifier with	null	false	MEDIUM
camel.sink.endpoint.folds	Number of folds to use for cross-validation	10	false	MEDIUM
camel.sink.endpoint.loadFrom	Path to load the model from	null	false	MEDIUM
camel.sink.endpoint.saveTo	Path to save the model to	null	false	MEDIUM
camel.sink.endpoint.seed	An optional seed for the randomizer	1	false	MEDIUM
camel.sink.endpoint.xval	Flag on whether to use cross-validation with the current dataset	false	false	MEDIUM
camel.sink.endpoint.path	An in/out path for the read/write commands	null	false	MEDIUM
camel.component.weka.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.weka.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

Name

Description

Default

Required

Priority

camel.sink.path.command

The command to use. One of: [filter] [model] [read] [write] [push] [pop] [version]

null

true

HIGH

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

The filter spec (i.e. Name Options)

null

false

MEDIUM

camel.sink.endpoint.build

The classifier spec (i.e. Name Options)

null

false

MEDIUM

camel.sink.endpoint.dsname

The named dataset to train the classifier with

null

false

MEDIUM

camel.sink.endpoint.folds

Number of folds to use for cross-validation

false

MEDIUM

camel.sink.endpoint.loadFrom

Path to load the model from

null

false

MEDIUM

camel.sink.endpoint.saveTo

Path to save the model to

null

false

MEDIUM

camel.sink.endpoint.seed

An optional seed for the randomizer

false

MEDIUM

camel.sink.endpoint.xval

Flag on whether to use cross-validation with the current dataset

false

MEDIUM

camel.sink.endpoint.path

An in/out path for the read/write commands

null

false

MEDIUM

camel.component.weka.lazyStartProducer

false

MEDIUM

camel.component.weka.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

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

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

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