Neo4j Streams 3.5.10

Dear community we're happy to announce the new 3.5.10 release of Neo4j Streams for Neo4j 3.5.x.
This release contains the following improvements:

• (#362) Source performance improvements: certain network configuration could lead to bad performance while you're using the CDC module; these have been identified and fixed.

Neo4j Streams 4.0.4 beta

The file contains a beta release containing the changes provided in #347.

This file is not meant for using in production environment.

4.0.3

New release

Neo4j Streams 3.5.10 beta

The file contains a beta release containing the changes provided in #362

Release 3.5.9

Hi community!
We are very proud to share the new release for Neo4j 3.5.x.
This release focuses on bug fixes and stability by improving the Neo4j lifecycle management (#344)

3.5.8

New release

3.5.7

New release

4.0.2

New release

4.0.1

New release

First Release for Neo4j v 4.0

Hi community!
We are very proud to share the first release of Streams Project for Neo4j 4.0 (here the docs).
This release supports the Multi database feature for sink and source in the following way.

Neo4j Streams: Source Module

You can set for each database instance a configuration suffix with the following pattern from.<DB_NAME> to the properties in your neo4j.conf file.

Following the list of new properties that allows to support multi-tenancy:

streams.source.topic.nodes.<TOPIC_NAME>.from.<DB_NAME>=<PATTERN>
streams.source.topic.relationships.<TOPIC_NAME>.from.<DB_NAME>=<PATTERN>
streams.source.enabled.from.<DB_NAME>=<true/false, default=true>
streams.procedures.enabled.<DB_NAME>=<true/false, default=true>

For more in-depth description, please got to the following doc page

Neo4j Streams: Sink Module

You can set for each database instance a configuration suffix with the following pattern to.<DB_NAME> to the properties in your neo4j.conf file.

Following the list of new properties that allows to support multi-tenancy:

streams.sink.topic.cypher.<TOPIC_NAME>.to.<DB_NAME>=<CYPHER_QUERY>
streams.sink.topic.cdc.sourceId.to.<DB_NAME>=<LIST_OF_TOPICS_SEPARATE_BY_SEMICOLON>
streams.sink.topic.cdc.schema.to.<DB_NAME>=<LIST_OF_TOPICS_SEPARATE_BY_SEMICOLON>
streams.sink.topic.pattern.node.<TOPIC_NAME>.to.<DB_NAME>=<NODE_EXTRACTION_PATTERN>
streams.sink.topic.pattern.relationship.<TOPIC_NAME>.to.<DB_NAME>=<RELATIONSHIP_EXTRACTION_PATTERN>
streams.sink.enabled.to.<DB_NAME>=<true/false, default=true>
streams.procedures.enabled.<DB_NAME>=<true/false, default=true>

For more in-depth description, please got to the following doc page

Multi Database Support

You can define into the json (or via the Confluent UI) a param named neo4j.database which is the targeted database name.

N.b. If no value is specified the connector will use the Neo4j's default db.