docs: Fix Flink retrieval compatibility notes#6498
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it
Updates the Flink compute engine reference docs to match the merged runtime behavior.
The Flink engine now prefers native
to_flink_table(table_env)retrieval jobs when available, but also supports the standardRetrievalJob.to_arrow()path by converting Arrow results into Flink tables. The docs still described Arrow/pandas-only retrieval jobs as unsupported, which is now stale.Does this PR introduce a user-facing change
Yes.
The documentation now accurately describes which offline-store retrieval paths are supported by the Flink compute engine.
Testing
Docs-only change.
Related
Follow-up to the merged Flink engine work in #6476.