FANNG1 opened a new pull request, #10442:
URL: https://github.com/apache/gravitino/pull/10442

   ### What changes were proposed in this pull request?
   
   This PR adds a Flink multi-version support spec under `ai-code-spec/` for 
Gravitino Flink connector.
   
   The spec covers:
   - the current Flink connector architecture and its main Flink interaction 
points
   - the proposed module split with `flink-common` plus versioned Flink modules 
and runtime modules
   - dependency matrix considerations for Flink `1.18`, `1.19`, and `1.20`
   - extension hooks for future `1.20` catalog API support
   - a future compatibility lane for Flink `2.0` that is explicitly out of 
scope for this delivery
   - testing, CI, and documentation expectations for the multi-version support 
work
   
   This PR also refines the spec metadata and narrows the real Flink 
environment requirement to a smoke-validation lane for this delivery.
   
   ### Why are the changes needed?
   
   The Flink connector currently targets a single Flink minor version. To 
support Flink `1.18`, `1.19`, and `1.20` in a maintainable way, the project 
needs a clear implementation spec that AI agents and human reviewers can follow 
consistently.
   
   This spec is intended to reduce ambiguity before the actual code split 
starts and to provide a common review baseline for follow-up implementation 
work.
   
   Fix: #9710
   
   ### Does this PR introduce _any_ user-facing change?
   
   No runtime user-facing behavior is changed in this PR.
   
   This PR adds a design/spec document only. It documents the intended 
multi-version support plan and the expected validation scope for future 
implementation work.
   
   ### How was this patch tested?
   
   This is a documentation/spec-only change.
   
   No automated tests were run.
   


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