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

   <!--
   
   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
   
   Refs #11355 and #11790.
   
   This PR documents the proposed backend contract for a bounded schema 
evolution timeline in Zeta Engine.
   
   The design defines:
   
   - correlation identity across source, transform, routing, and sink stages
   - execution-attempt-aware deduplication without guessing replay identity
   - explicit multi-target outcomes, including partial application and targets 
skipped by fail-fast behavior
   - best-effort recording that cannot alter schema-change, checkpoint, or job 
results
   - fixed retention, attempt, target, and error-summary bounds with visible 
truncation
   - one REST model for running and finished jobs without exposing raw DDL by 
default
   - compatibility requirements for existing schema events and job-info behavior
   
   English and Chinese documentation are included. The relationship with #11402 
is explicit: that issue continues to own schema ordering, replay, restore, and 
correctness semantics.
   
   This PR is intentionally limited to the design. Runtime capture, storage, 
REST, E2E, and Web UI work will follow in separate issues after the contract is 
approved.
   
   ### Does this PR introduce _any_ user-facing change?
   
   Yes. It adds English and Chinese documentation describing the proposed 
schema evolution timeline contract.
   
   It does not change current runtime behavior, configuration, or public APIs.
   
   ### How was this patch tested?
   
   Validated the sidebar syntax, bilingual document structure, code-fence 
balance, and patch whitespace.
   
   ```shell
   node --check docs/sidebars.js
   git diff --check
   ```
   
   No runtime tests were added because this PR only introduces design 
documentation.
   
   ### Check list
   
   * [ ] If any new Jar binary package adding in your PR, please add License 
Notice according
     [New License 
Guide](https://github.com/apache/seatunnel/blob/dev/docs/en/developer/new-license.md)
   * [x] If necessary, please update the documentation to describe the new 
feature. https://github.com/apache/seatunnel/tree/dev/docs
   * [ ] If necessary, please update `incompatible-changes.md` to describe the 
incompatibility caused by this PR.
   * [ ] If you are contributing the connector code, please check that the 
following files are updated:
     1. Update 
[plugin-mapping.properties](https://github.com/apache/seatunnel/blob/dev/plugin-mapping.properties)
 and add new connector information in it
     2. Update the pom file of 
[seatunnel-dist](https://github.com/apache/seatunnel/blob/dev/seatunnel-dist/pom.xml)
     3. Add ci label in 
[label-scope-conf](https://github.com/apache/seatunnel/blob/dev/.github/workflows/labeler/label-scope-conf.yml)
     4. Add e2e testcase in 
[seatunnel-e2e](https://github.com/apache/seatunnel/tree/dev/seatunnel-e2e/)
     5. Update connector 
[plugin_config](https://github.com/apache/seatunnel/blob/dev/config/plugin_config)
   


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