camel-optaplanner-kafka-connector sink configuration

When using camel-optaplanner-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-optaplanner-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.optaplanner.CamelOptaplannerSinkConnector

The camel-optaplanner sink connector supports 11 options, which are listed below.

Name	Description	Default	Required	Priority
camel.sink.path.configFile	Specifies the location to the solver file. If useSolverManager=FALSE, Camel uses this file and create the Solver. If useSolverManager=TRUE and SolverManager is set in the header {OptaPlannerConstants.SOLVER_MANAGER} : this file is ignored by Camel usage of SolverManager. SolverManager can be injected by DI in Quarkus or Spring.	null	true	HIGH
camel.sink.endpoint.problemId	In case of using SolverManager : the problem id	"1L"	false	MEDIUM
camel.sink.endpoint.solverId	Specifies the solverId to user for the solver instance key	"DEFAULT_SOLVER"	false	MEDIUM
camel.sink.endpoint.useSolverManager	use SolverManager instead of XML file config. Use this mode on Quarkus app.	false	false	MEDIUM
camel.sink.endpoint.async	Specifies to perform operations in async mode	false	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.threadPoolSize	Specifies the thread pool size to use when async is true	10	false	MEDIUM
camel.sink.endpoint.basicPropertyBinding	Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	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.component.optaplanner.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.optaplanner.basicPropertyBinding	Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities	false	false	LOW

Name

Description

Default

Required

Priority

camel.sink.path.configFile

Specifies the location to the solver file. If useSolverManager=FALSE, Camel uses this file and create the Solver. If useSolverManager=TRUE and SolverManager is set in the header {OptaPlannerConstants.SOLVER_MANAGER} : this file is ignored by Camel usage of SolverManager. SolverManager can be injected by DI in Quarkus or Spring.

null

true

HIGH

camel.sink.endpoint.problemId

In case of using SolverManager : the problem id

"1L"

false

MEDIUM

camel.sink.endpoint.solverId

Specifies the solverId to user for the solver instance key

"DEFAULT_SOLVER"

false

MEDIUM

camel.sink.endpoint.useSolverManager

use SolverManager instead of XML file config. Use this mode on Quarkus app.

false

MEDIUM

camel.sink.endpoint.async

Specifies to perform operations in async mode

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

Specifies the thread pool size to use when async is true

false

MEDIUM

camel.sink.endpoint.basicPropertyBinding

Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

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.component.optaplanner.lazyStartProducer

false

MEDIUM

camel.component.optaplanner.basicPropertyBinding

Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities

false

LOW

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

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

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