v2.6.0

What's Changed

The test thats been changed revealed that wrap around wasn't handled correctly.

When wrap around happens the max would be the lower value and the valid through the higher number.

Fix is implemented at both a per partition level and at topic commit level.

v2.5.0

What's Changed

• Snapshots created in iceberg now contain metadata the indicates the commit type. These can either be full or partial

Full Changelog: rapid7:v2.4.0...rapid7:v2.5.0

v2.4.0

What's Changed - NEED TO COMPLETE USD-3455 BEFORE RELEASING

• Reverted the applySchemaless() method to populate source_ts_ms instead of source_ts_us tas historical cdc data is gonna be removed

Full Changelog: rapid7:v2.3.0...rapid7:v2.4.0

v2.3.0

What's Changed

Pulls in patch changes from v1.3.3

Pulls in changes from v2.2.0

v2.2.0

What's Changed - NEED TO COMPLETE USD-3509 + USD-3455 BEFORE RELEASING

• Updated DebeziumTransform to read the correct field for source_ts_ms, It will now populate it with ts of the event in source db instead of the ts of the event is picked up by Debezium
• Reverted the applySchemaless() method to populate source_ts_us instead of source_ts_ms to support historical cdc data

Full Changelog: rapid7:v2.1.1...rapid7:v2.2.0

v1.3.3

only to be used in govcloud

bump netty-codec to 4.1.125.Final

bump commons-lang3 and logback

v2.1.1

What's Changed

Further fixes to TXID metadata calculations:

• Reverts Transaction Data Complete message so that it can be handled

Full Changelog: rapid7:v2.1.0...rapid7:v2.1.1

v2.1.0

Broken Release Do Not Use

What's Changed

Further fixes to TXID metadata calculations:

• Changes the coordinator commitTxIdsByTable from a nested commit map to a single table identifier to list of topic txid map.
• This new map is populated when the coordinator receives a datawritten message instead of the complete message and cleared directly after the commitbuffer to ensure there is a corresponding transaction data for every file that is to be written.

Full Changelog: rapid7:v2.0.0...rapid7:v2.1.0

v2.0.0

Broken Release Do Not Use

What's Changed

Fixes TXID metadata calculations:

• New TXID Tracking Map: Introduced a new map with the structure commit uuid -> table name -> topic partition object -> txid for more granular and accurate transaction ID tracking.
• Table Context Propagation: A new class was created to pass the table object into the coordinator's context. This provides the necessary table-level information for the new mapping. Dependent classes were updated to use this new context.
• Centralized TXID Extraction: The responsibility for extracting transaction IDs has been moved to the Iceberg writer class. The extracted txids are now passed back within the written data results, streamlining the data flow.
• Thread Safety: Implemented additional synchronization to ensure the new data structures are managed safely in a multi-threaded environment.
• Empty File Filtering: Added logic to detect and filter out data files with zero records, preventing them from improperly influencing the txid metadata calculations.
• Single Partition Valid Through: Added a partition check so on single partition topics the valid through no longer removes 1 keeping the data more up to date especially in low flowing topics improving test results and data lag as we are no longer unnecessarily holding onto the last transaction.

Full Changelog: rapid7:v1.3.2...rapid7:v2.0.0

v1.3.2

Patch jackson vulnerability - 2.15.0 is not vulnerable

This release was initially to bump jetty to 12.0.12 which is not possible, has been reverted