Source Configuration Settings
Connector Settings
| Name | Description |
|---|---|
|
|
|
A compatible Kafka Connect converter. Could be one of;
|
|
Schema Registry URL for message keys.
Required when a schema registry is required by the configured |
|
Should be set to |
|
A compatible Kafka Connect converter. Could be one of;
|
|
Schema Registry URL for message values.
Required when a schema registry is required by the configured |
|
Should be set to |
Neo4j Connection Settings
| Name | Description |
|---|---|
|
Neo4j URI to connect to. Multiple URIs can be specified separated by |
|
Neo4j database name to connect to. Recommended to be specified explicitly. |
|
Authentication type to use.
One of Default: |
|
Username to authenticate with.
Required when |
|
Password to authenticate with.
Required when |
|
Authentication realm to authenticate with, leave empty for default. |
|
Kerberos ticket to establish connection with.
Required when |
|
Bearer token to establish connection with.
Required when |
|
Custom authentication scheme to establish connection with.
Required when |
|
Custom principal to establish connection with.
Required when |
|
Custom credential to establish connection with.
Required when |
|
Custom authentication realm to authenticate with, set as required by your custom authentication provider. |
|
TCP connection timeout (valid units are: Default: |
|
Maximum number of connections to keep in the connection pool. Default: |
|
Maximum duration to wait for acquiring a connection from the connection pool (valid units are: Default: |
|
Duration after which idle connections are tested for liveness (valid units are: Default: |
|
Duration after which a connection is dropped from the connection pool (valid units are: Default: |
|
Maximum duration to retry a transaction. Default: |
|
Whether encryption is enabled. Only applicable when Default: |
|
Trust strategy to use for TLS connections.
One of Default: |
|
List of files that contain X509 certificates of CAs to trust.
Required when |
|
Whether hostname verification is enabled during TLS handshake.
One of Default: |
Common Source Settings
| Name | Description |
|---|---|
|
Source strategy for this connector.
One of |
|
A time anchor to start streaming from.
One of Default: |
|
Custom value to use as a starting offset.
Required when |
|
Whether to ignore any offset value retrieved from the offset storage saved by a previous run.
One of Default: |
|
Maximum number of change events to publish for each poll cycle. Default: |
|
Defines the structure of change messages. One of Default: |
CDC Strategy Settings
| Name | Description |
|---|---|
|
Serialisation strategy for CDC topic key.
One of Default: For guidance on choosing a strategy, see Best practices for Source connector. |
|
Serialisation strategy for CDC topic value.
One of Default: Note: If you’re using a sink connector with one of the CDC strategies, this setting must be configured as |
|
Maximum amount of time Kafka Connect poll request will wait for a change to be received from the database (valid units are: Default: |
|
The interval in which the database will be polled for changes during Default: |
|
Comma-separated list of graph patterns, with optional event property filters (prefixed with Example setting: For guidance on choosing between this form and the indexed form below, see Choosing between the list and indexed forms. |
|
Indexed graph pattern, with optional event property filters (prefixed with Example: |
|
One of Example: |
|
Comma-separated list of property names. Example: |
|
User who was authenticated while performing the change. Example: |
|
User who was executing the transaction while performing the change.
Usually will be same with Example: |
|
Key-value transaction metadata selector. The key-value pair is matched against the actual transaction metadata (with the key stripped of the aforementioned prefix). Example: |
|
Whether to enable the Default: |
|
The refresh interval of the Default: |
|
Whether to always run CDC queries against the leader instance of the database, instead of any cluster member. For guidance on choosing between the two, see Decide whether to pin CDC queries to the leader. Default: |
QUERY strategy Settings
| Name | Description |
|---|---|
|
Kafka topic to publish change events gathered through provided query. |
|
Cypher query to use for gathering changes.
Requires both |
|
Property name that is both present in the result set of the specified query and used as a filter to query changes from a previous value. Default: |
|
Maximum amount of time Kafka Connect poll request will wait for a change to be received from the database (valid units are: Default: |
|
The interval in which the database will be polled for changes during Default: |
|
Maximum amount of time query is allowed to run (valid units are: Default: |
|
This forces the schema encoding of map values to be structs (default: |