nzw921rx opened a new pull request, #10604:
URL: https://github.com/apache/seatunnel/pull/10604

   #10596
   
   <!--
   
   Thank you for contributing to SeaTunnel! Please make sure that your code 
changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   ## Contribution Checklist
     - Make sure that the pull request corresponds to a [GITHUB 
issue](https://github.com/apache/seatunnel/issues).
     - Name the pull request in the form "[Feature] [component] Title of the 
pull request", where *Feature* can be replaced by `Hotfix`, `Bug`, etc.
     - Minor fixes should be named following this pattern: `[hotfix] [docs] Fix 
typo in README.md doc`.
   -->
   
   ### Purpose of this pull request
   
   Add a `sample-sharding.enable` option for CDC connectors and 
`split.sample-sharding.enable` for JDBC connector,
   
   
   ### Does this PR introduce _any_ user-facing change?
   
   New optional config:
   - JDBC: `split.sample-sharding.enable` (Boolean, default `true`)
   - CDC (MySQL/Oracle/PG/SQLServer): `sample-sharding.enable` (Boolean, 
default `true`)
   
   When set to `false`, the system should fall back to unevenly-sized chunk 
splitting (iterative query approach) regardless of the shard count.
   
   ### How was this patch tested?
   
   - Unit test in `DynamicChunkSplitterTest`: verifies config parsing and 
default value
   - E2E test in `JdbcMysqlSplitIT`: verifies that `enable=true` uses sampling 
path while `enable=false` falls back to unevenly-sized chunk splitting, 
producing different split counts
   
   
   
   ### Check list
   
   *  Documentation updated (en & zh) for JDBC, MySQL-CDC, Oracle-CDC, 
PostgreSQL-CDC, SqlServer-CDC
   *  No incompatible changes (default `true`, fully backward compatible)
   


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