camel-xquery-kafka-connector sink configuration

Connector Description: Query and/or transform XML payloads using XQuery and Saxon.

When using camel-xquery-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-xquery-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.xquery.CamelXquerySinkConnector

The camel-xquery sink connector supports 19 options, which are listed below.

Name Description Default Required Priority

camel.sink.path.resourceUri

The name of the template to load from classpath or file system

null

true

HIGH

camel.sink.endpoint.allowStAX

Whether to allow using StAX mode

false

false

MEDIUM

camel.sink.endpoint.headerName

To use a Camel Message header as the input source instead of Message body.

null

false

MEDIUM

camel.sink.endpoint.namespacePrefixes

Allows to control which namespace prefixes to use for a set of namespace mappings

null

false

MEDIUM

camel.sink.endpoint.resultsFormat

What output result to use One of: [Bytes] [BytesSource] [DOM] [DOMSource] [List] [String] [StringSource]

"DOM"

false

MEDIUM

camel.sink.endpoint.resultType

What output result to use defined as a class

null

false

MEDIUM

camel.sink.endpoint.stripsAllWhiteSpace

Whether to strip all whitespaces

true

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

To use a custom Saxon configuration

null

false

MEDIUM

camel.sink.endpoint.configurationProperties

To set custom Saxon configuration properties

null

false

MEDIUM

camel.sink.endpoint.moduleURIResolver

To use the custom ModuleURIResolver

null

false

MEDIUM

camel.sink.endpoint.parameters

Additional parameters

null

false

MEDIUM

camel.sink.endpoint.properties

Properties to configure the serialization parameters

null

false

MEDIUM

camel.sink.endpoint.staticQueryContext

To use a custom Saxon StaticQueryContext

null

false

MEDIUM

camel.component.xquery.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.xquery.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.xquery.configuration

To use a custom Saxon configuration

null

false

MEDIUM

camel.component.xquery.configurationProperties

To set custom Saxon configuration properties

null

false

MEDIUM

camel.component.xquery.moduleURIResolver

To use the custom ModuleURIResolver

null

false

MEDIUM

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

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

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

Back to top