camel-graphql-kafka-connector sink configuration

When using camel-graphql-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-graphql-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.graphql.CamelGraphqlSinkConnector

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

Name Description Default Priority

camel.sink.path.httpUri

The GraphQL server URI.

null

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

The query or mutation name.

null

MEDIUM

camel.sink.endpoint.proxyHost

The proxy host in the format hostname:port.

null

MEDIUM

camel.sink.endpoint.query

The query text.

null

MEDIUM

camel.sink.endpoint.queryFile

The query file name located in the classpath.

null

MEDIUM

camel.sink.endpoint.variables

The JsonObject instance containing the operation variables.

null

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

The access token sent in the Authorization header.

null

MEDIUM

camel.sink.endpoint.password

The password for Basic authentication.

null

MEDIUM

camel.sink.endpoint.username

The username for Basic authentication.

null

MEDIUM

camel.component.graphql.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.component.graphql.basicPropertyBinding

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

false

MEDIUM

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

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

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