DanielLeens commented on issue #11741: URL: https://github.com/apache/seatunnel/issues/11741#issuecomment-5917735689
Classification: F / JDBC source split planning, covered by an active PR. Thanks for offering to help. I checked current `dev` and the open PR set: #11746 already owns this exact JDBC composite-primary-key chunk-splitting scope. It changes the same `ChunkSplitter` and `DynamicChunkSplitter` path and is currently awaiting resolution of its failed Build, so assigning a second implementation would duplicate and conflict with that work. Please do not open a parallel fix. The most useful contribution now is to review #11746's dialect and boundary coverage, especially repeated first-key values, NULL key components, tuple-boundary inclusivity, and the unchanged single-column fallback. Please report any concrete gap on that PR; once its current implementation path is resolved or closed, this issue can be reassessed for a new assignee. -- 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]
