Known Issues

This feature has been released as a public beta in AuraDB Enterprise October Release and Neo4j Enterprise Edition 5.13 and breaking changes are likely to be introduced before it is made generally available (GA).

Neo4j 5.18

As of Neo4j 5.18 the CDC feature has the following known issues.

Unstable elementId

CDC returns the same elementId as provided by the elementId() function. This elementId is not stable through processes that change the underlying database such as:

  • Restoring from backup

  • Copying the database to a new name or location.

  • Pausing and resuming the database in Neo4j Aura.

This means that performing any of the listed actions causes new changes to the same element to be transmitted with a different elementId.

It is recommended that logical / business keys are used to identify elements. See The role of elementIds and key properties for details on logical / business keys.

Unstable changeId

The change identifier which CDC uses to track the location in the transaction log has similar issues as the elementId. The actions listed under Unstable elementId also cause change identifiers to become invalid. After performing any of these actions it might be required to restart querying changes from db.cdc.current or db.cdc.earliest.