Merge pull request #56 from telefonicaid/update-cnr-and-doc

Update CNR and doc

Author: AlvaroVega

CHANGES_NEXT_RELEASE

@@ -0,0 +1,2 @@
+- Update: JDBC upsert now allows updates when `updateIfNewerField` has the same value (`>=` instead of `>`), and skips the freshness check when the field is missing in the incoming record (telefonicaid/kafka-connect-jdbc-postgis#260)
+- Upgrade kafka-connect-jdbc for postgis from 10.9.2 to 10.9.3 (#50)

doc/technical_configuration.md

@@ -764,6 +764,24 @@ For PostGIS sinks, a batch size of **3000** has proven to be a good default unde
 
 ---
 
+## ⏱️ Conditional Upserts with `updateIfNewerField`
+
+For JDBC sinks using `insert.mode=upsert`, the optional parameter:
+
+```json
+"updateIfNewerField": "recvtime/timeinstant"
+```
+
+prevents existing rows from being updated with older data.
+
+When configured, the connector only performs the update if the incoming value is **greater than or equal to** the value already stored in the database.
+
+If the field specified in `updateIfNewerField` is not present in the incoming record, the upsert is executed normally without applying the freshness check.
+
+This feature is typically used by *lastdata* flows to avoid overwriting newer observations with stale data.
+
+---
+
 ## ▶️ Registering Connectors (it will be updated)
 
 From the `sinks/` directory, register each connector using `curl`:
@@ -809,4 +827,4 @@ Check tables in PostGIS or MongoDB after running the corresponding test input.
 
 For complete operational guidance, multi-tenant management, and security best practices, please refer to the **Kafnus main repository**:
 
-- [Advanced Topics](https://github.com/telefonicaid/kafnus/blob/main/doc/03_advanced_topics.md) – security and operational guide.
+- [Advanced Topics](https://github.com/telefonicaid/kafnus/blob/main/doc/03_advanced_topics.md) – security and operational guide.