[gg-mskm]

Description

In the RDS source's CDC/binlog stream mode, BinlogEventListener keeps an in-memory tableId -> TableMetadata map (tableMetadataMap) that is populated from binlog TABLE_MAP events. handleTableMapEvent returned early for any table that is not of interest without touching the map, so an entry recorded for a table of interest survived indefinitely and was never invalidated.

The binlog table_id is not stable: the server assigns it from its table definition cache and can reassign it to a different table across a server restart (and when a table is evicted from and reloaded into the cache). When a table_id previously bound to a synced table is reassigned to a non-synced table, isValidTableId still accepts the row events because the stale entry is present and points at a synced table. Those rows are then decoded with the wrong column definitions, which silently writes corrupted documents to the sink (for example a byte-array name rendered as [B@30fb30c]) and raises type-conversion errors for rows whose types do not line up. This reproduces on routine operational events such as an Aurora reboot, maintenance, or failover.

This change removes the mapping held for a table_id whenever a TABLE_MAP event shows that the id now refers to a table that is not of interest, so subsequent row events for that id are skipped as intended. Mappings for tables of interest are unaffected; they are already overwritten on every TABLE_MAP event.

Verification:

• Added 3 unit tests to BinlogEventListenerTest. Without the fix the stale-mapping test fails (isValidTableId returns true for a reassigned id); with the fix all tests pass.
• End-to-end on Aurora MySQL 8.0 (aurora-mysql 3.10.4): after forcing a table_id collision across a reboot, the unfixed build reproduces the Row data length (25) does not match column names size (21) WARN and writes corrupted documents, while the fixed build removes the stale entry, skips the non-synced rows, and writes no corrupted documents. Synced-table replication is unchanged in both cases.

Issues Resolved

Resolves #7125

Check List

• New functionality includes testing.
• New functionality has a documentation issue. Please link to it in this PR.
  • New functionality has javadoc added
• Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🧪 PR contains tests

🔒 No security concerns identified

✅ No TODO sections

🔀 No multiple PR themes

⚡ No major issues detected

[graytaylor0]

Thanks for addressing this!