Suhel0328 opened a new pull request, #4481:
URL: https://github.com/apache/flink-cdc/pull/4481

   ## What is the purpose of the change
   
   Fixes 7 runtime errors that prevent the Oracle CDC connector from working 
with Oracle 26ai (CDB/PDB mode) when using Debezium 3.4.2.Final. Also applies 
the required Debezium 3.x API compatibility fixes across all JDBC source 
connectors (MySQL, DB2, Postgres, SQL Server) that result from the version 
upgrade.
   
   JIRA: https://issues.apache.org/jira/browse/FLINK-40201
   
   ## Brief change log
   
   - Fix `NoSuchMethodError` on `LogMinerChangeRecordEmitter` (10-arg → 9-arg 
constructor to match Debezium 3.4.2)
   - Add `ResumePositionProvider` local override: `sessionContext` null-guard 
and `database.*` prefix strip
   - Fix `ORA-01031`: use `ALL_TABLES.NUM_ROWS` instead of `ANALYZE TABLE`
   - Fix schema recovery in CDB/PDB mode with catalog-agnostic `TableFilter`
   - Guard `isRecordBetween()` against absent ROWID Connect header (Debezium 
3.4.2 no longer injects it)
   - Include `debezium-common` in shade assembly to prevent 
`ClassNotFoundException`
   - Add `EmbeddedFlinkSchemaHistory` / `RelationalDatabaseSchema` for Debezium 
3.x API
   - Upgrade `DatabaseHistory` → `SchemaHistory`, `SchemaNameAdjuster` package, 
`TopicSelector` → `TopicNamingStrategy` across all JDBC connectors
   
   ## Verifying this change
   
   Tested end-to-end: Oracle 26ai FREE (CDB + FREEPDB1) → Flink CDC 
3.6-SNAPSHOT → StarRocks sink.
   
   - Snapshot: 3 rows confirmed in StarRocks
   - Streaming CDC: live UPDATE propagated correctly within expected flush 
interval
   
   ## AI Disclosure
   
   - [x] I used AI tools (Claude Code, Anthropic) to assist with this 
contribution. I have reviewed, tested, and verified all changes.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to