Docs: Document reading in Spark using branch and tag identifiers #9238
Conversation
This file contains 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
|
@rdblue @jackye1995 @amogh-jahagirdar what do you think? |
nastra
approved these changes
Dec 7, 2023
This was referenced Dec 11, 2023
lisirrx
pushed a commit
to lisirrx/iceberg
that referenced
this pull request
Jan 4, 2024
devangjhabakh
pushed a commit
to cdouglas/iceberg
that referenced
this pull request
Apr 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Writing to a branch or tag is supported in Spark using a table identifier with
branch_<branchname>ortag_<tagname>. Reading from the branch or tag is supported using the same kind of identifier, in addition to theVERSION AS OFsyntax, but this is not documented. For consistency, users may prefer to read and write using the same syntax. We should document that they can.Note: When loading a table using identifiers with
snapshot_id_andat_timestamp_was implemented, this was considered an implementation detail and we did not expose it publicly (i.e., document it). However, since thebranch_andtag_identifiers are used for writes and documented, we should expose them for reads as well.