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

   ## What is the purpose of this pull request?
   
   Align SQL Server Pipeline connector defaults with the SQL Server SQL API 
defaults for snapshot backfill and unbounded chunk assignment.
   
   ## Brief change log
   
   - Change `scan.incremental.snapshot.backfill.skip` default from `true` to 
`false` for SQL Server Pipeline connector.
   - Change `scan.incremental.snapshot.unbounded-chunk-first.enabled` default 
from `false` to `true` and remove stale default wording.
   - Update English and Chinese SQL Server Pipeline docs, including 
compatibility notes for restoring old Pipeline behavior.
   - Add a factory regression test to verify the effective forwarded defaults.
   
   ---
   
   ## Verifying this change
   
   This change added tests and can be verified as follows:
   
   - Added unit coverage in 
`SqlServerDataSourceFactoryTest#testSnapshotBackfillAndUnboundedChunkFirstDefaults`.
   - Ran `mvn spotless:apply`.
   - Ran `mvn -pl 
flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-sqlserver
 -DskipTests package`.
   - Attempted `mvn -pl 
flink-cdc-connect/flink-cdc-pipeline-connectors/flink-cdc-pipeline-connector-sqlserver
 
-Dtest=SqlServerDataSourceFactoryTest#testSnapshotBackfillAndUnboundedChunkFirstDefaults
 test`, but local Testcontainers startup was blocked by Docker client/API 
configuration.
   
   ## Documentation
   
   - Does this pull request introduce a new feature? no
   - If yes, how is the feature documented? docs
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (Apache OpenAI Codex)
   
   Generated-by: Apache OpenAI Codex
   


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