davidzollo opened a new issue, #11043: URL: https://github.com/apache/seatunnel/issues/11043
## Background SeaTunnel CDC schema evolution is currently controlled mainly as an enable/disable capability. That is not expressive enough for production jobs that need different reactions to schema changes. Some users want strict failure on any schema change, while others need best-effort evolution or a more lenient mode for multi-table synchronization. ## Proposed change Introduce policy-level schema change behavior modes for CDC jobs instead of only a binary switch. ## Expected behavior Examples of useful policies include: - fail immediately on unsupported or unexpected schema change - apply schema change automatically when possible - apply best effort and fail only when reconciliation is impossible - lenient handling for selected classes of schema changes The final naming can be decided during implementation, but the behavior model should be explicit and documented. ## Acceptance criteria - Schema evolution behavior can be configured via a clear policy option. - The policy is applied consistently in CDC source-to-sink schema change flow. - Failure semantics are documented for each policy mode. - English and Chinese docs are updated. - Add focused tests covering at least strict and permissive policy paths. ## Out of scope - Connector-specific startup mode work. - Filtering individual schema change event types by name. - Route/transform DSL enhancements. -- 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]
