MartijnVisser opened a new pull request, #29934:
URL: https://github.com/apache/flink/pull/29934

   ## What is the purpose of the change
   
   The upgrading page only covers the DataStream API, and the concepts page 
still says savepoints only work when both the query and the Flink version stay 
the same. Both are outdated with compiled plans and PTFs.
   
   ## Brief change log
   
   - `upgrading.md`: new Table API & SQL section
   - `overview.md`: document `COMPILE AND EXECUTE PLAN`, replace the outdated 
upgrade text with a link
   - `ptfs.md`: link the state and UID sections to the new section
   - zh pages get the English text, the outdated Chinese paragraphs are removed
   - Hotfix commit: fix the `COMPILE PLAN` and `EXECUTE PLAN` syntax
   
   ## Verifying this change
   
   Docs only. I checked the statements with restore runs of a PTF job on 2.2.1, 
2.3.0 and master, with and without a compiled plan. Not run: the `flink` CLI 
commands, the SQL Client `SET` form, source start positions, and a query that a 
newer version plans differently.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): no
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude Code (Claude Opus 5.5)
   


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