Configuration Summary
Following a summary of all the configuration parameters you can use for the Kafka Connect Neo4j Connector:
Name | Value | Mandatory | Note |
---|---|---|---|
|
|
|
|
|
|
|
Converter class for key Connect data |
|
|
|
Converter class for value Connect data |
|
|
|
If true the key will be treated as a composite JSON object containing schema and the data. Default value is false |
|
|
|
If true the value will be treated as a composite JSON object containing schema and the data. Default value is false |
|
|
|
The Schema Registry URL has to be provided only when you decide to use AvroConverter |
|
|
|
The Schema Registry URL has to be provided only when you decide to use AvroConverter |
|
|
|
Specify a database name only if you want to use a non-default database. Default value is 'neo4j' |
|
|
|
Neo4j Server URI |
|
|
|
Neo4j username |
|
|
|
Neo4j password |
|
|
|
The authentication realm |
|
|
|
The Kerberos ticket |
|
|
|
The authentication type (default: 'BASIC') |
|
|
|
The max number of events processed by the Cypher query (default: 1000) |
|
|
|
The execution timeout for the cypher query (default: 0, that is without timeout) |
|
|
|
The max Neo4j connection lifetime (default: 1 hour) |
|
|
|
The max Neo4j acquisition timeout (default 1 hour) |
|
|
|
The max Neo4j liveness check timeout (default 1 hour) |
|
|
|
The max pool size (default: 100) |
|
|
|
The path of the certificate |
|
|
|
|
|
|
|
The Neo4j trust strategy (default: TRUST_ALL_CERTIFICATES) |
|
|
|
The time in milliseconds to wait following a transient error before a retry attempt is made (default: 30000). |
|
|
|
The maximum number of times to retry on transient errors (except for TimeoutException) before failing the task (default: 5). |
Name | Value | Mandatory | Note |
---|---|---|---|
|
|
|
A list of comma-separated topics |
|
|
|
The Broker URI is mandatory only when if you have configured DLQ |
|
|
||
|
|
|
all == lenient, silently ignore bad messages. none (default) means that any error will result in a connector failure |
|
|
|
log errors (default: false) |
|
|
|
log bad messages too (default: false) |
|
|
|
dead letter queue topic name, if left off no DLQ, default: not set |
|
|
|
enrich messages with metadata headers like exception, timestamp, org. topic, org.part, default:false |
|
|
|
common prefix for header entries, e.g. |
|
|
|
replication factor, need to set to 1 for single partition, default:3 |
|
|
|
If enabled messages are processed concurrently in the sink. Non concurrent execution supports in-order processing, e.g. for CDC |
|
|
|
|
|
|
|
default value is SourceEvent |
|
|
|
default value is sourceId |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Name | Value | Mandatory | Note |
---|---|---|---|
|
|
|
The topic where the Source will publish the data |
|
|
|
The number of partition for the Source (default 1) |
|
|
|
When the Source connector starts:
|
|
|
|
The type of the Source strategy, with QUERY you must set |
|
|
|
The Cypher query in order to extract the data from Neo4j you need to define it if you use |
|
|
|
The name of the property that we need to consider in order to determinate the last queried record;
if not defined we use an internal value given from the last performed check.
We use this value for injecting it in the provided query defined in |
|
|
|
The polling interval in ms (Default: 10000) |
|
|
|
Apply a schema to each record (Default: false) |
|
|
|
The strategy that determines how message keys are serialized, based on the corresponding change event (Default: |
If you need to manage data in JSON format without using the Schema Registry, then you can use the
Other supported converters are:
Please see the following for further details: https://docs.confluent.io/home/connect/userguide.html#connect-configuring-converters For further information about Kafka Connect properties, please checkout the following: For further details about error handling properties refers to How deal with bad data section |
Kafka Connect Neo4j Connector supports also the secured Neo4j URI schemes. Please see the Neo4j official documentation for detailed information: https://neo4j.com/docs/driver-manual/current/client-applications/#driver-configuration-examples