Release 5.1.4 (#62)

Author: ali-ince

antora.yml

@@ -12,7 +12,7 @@ asciidoc:
     page-product: Neo4j Connector for Kafka
     kafka-connect-version: 3.0
     connector-version: '5.1'
-    exact-connector-version: '5.1.3'
+    exact-connector-version: '5.1.4'
     page-pagination: true
     product-name: Neo4j Connector for Kafka
     url-common-license-page: https://neo4j.com/docs/license/

modules/ROOT/pages/changelog.adoc

@@ -2,6 +2,24 @@
 
 This page lists changes to the {product-name}.
 
+== Version 5.1.4
+
+=== New and updated features
+
+[cols="2",options="header"]
+|===
+| Feature
+| Details
+
+a|
+label:bug[]
+label:fixed[]
+
+Fixed a bug in the CDC schema sink connector where relationship update and delete events without any start or end node keys incorrectly generated Cypher statements.
+a| Resolved an issue where messages referring to relationship update and delete events, which do not contain any start or end node keys, generate Cypher statements that update or delete wider entities on the target database.
+These messages now generate a failure which should be handled through xref:sink/error-handling.adoc[usual error handling] mechanisms.
+|===
+
 == Version 5.1.3
 
 === New and updated features
@@ -19,6 +37,7 @@ Fixed a bug in the Sink connector where messages without valid constraints would
 a| Resolved an issue where messages created from the `neo4j-streams` 4.1 source plugin, which include unique constraints without a corresponding value in the entity, result in a Cypher query containing null property filters to match on.
 Depending on the operation type (`UPDATE/DELETE/CREATE`), this can cause unexpected behavior as the query may not match the intended nodes.
 |===
+
 == Version 5.1.2
 
 === New and updated features

modules/ROOT/pages/known-issues.adoc

@@ -2,12 +2,4 @@
 = Known Issues
 :description: This chapter describes known issues related to {product-name}.
 
-== 5.1.0-rc02
-
-No known issues at this time.
-
-== 5.1.0-rc01
-
-* label:added[Resolved] Source connector with CDC strategy is being killed when it receives a change event that contains an update of type for a property.
-An example of such a change is when a node that has a property named `age` was set to a string value of `"25"`, but updated to be an `int` value of `25`.
-Change events with this condition will break schema derivation in the connector and a fix is being implemented to address this.
+_No known issues at this time._

modules/ROOT/pages/whats-new.adoc

@@ -32,6 +32,7 @@ It is no longer possible to turn off this behavior in the connector itself, and
 * Error handling is re-implemented to provide full integration with Kafka Connect infrastructure, and failing messages can be identified and forwarded to Dead Letter Queues (if configured) independently.
 
 * Both link:{page-canonical-root}/cdc[Change Data Capture] and previous streams plugin generated change event messages are supported in CDC strategies.
+Change events that cannot be processed for reasons such as invalid schema (no key fields, etc.) will no longer be silently ignored, but cause failures which must be monitored and handled through xref:sink/error-handling.adoc[error handling] mechanisms.
 
 * All message fields, including message timestamp as stored in Kafka, message headers, key and value can be referenced in Cypher strategy.