goutamadwant commented on issue #13223:
URL: https://github.com/apache/seatunnel/issues/13223#issuecomment-6815262722

   I would like to take the `JDBC / normal` row for the two key-routing gaps 
noted in #13221: a `byte[]` key is hashed by identity, and the declared key 
index is stale after a schema change moves the key column.
   
   I have a fix with unit tests: `MultiTableSinkWriter` hashes `byte[]` keys by 
content and re-reads each sub-writer's `primaryKey()` after the schema-change 
barrier; `JdbcSinkWriter` tracks the key column by name, follows a rename and 
recomputes the index after `applySchemaChange`. Full `seatunnel-api` and 
`connector-jdbc` unit suites pass on JDK 11 and 17. It keeps the existing keyed 
hash and does not touch the capability contract, so it should rebase onto Phase 
1 once that lands. I can open the PR now or after Phase 1, whichever you prefer.
   


-- 
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