Support snapshot queries on Iceberg system tables - custom IcebergSystemTableHandle extends SystemTableHandle #13854
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.
Description
Add the ability of querying Iceberg system tables by using
time travel queries either by snapshot or by timestamp.
Previously there were supported versioned queries on system
tables because the snapshot id could be encoded within the
table name:
The syntax mentioned previously is now deprecated and
replaced by a richer syntax:
SystemTableHandle
has been transformed to an interfaceand was moved to
trino-spi
for being able to add acustom implementation for this interface for the Iceberg
connector which supports time travel on the metadata
tables.
Bugfix
Iceberg connector
The metadata tables exposed by the Iceberg connector for its tables should support snapshot/versioned queries in the same fashion as the Iceberg tables.
Related issues, pull requests, and links
Fixes #12736
This PR offers a different approach to #13497 by extending SystemTableHandle for Iceberg time travel queries needs.
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
() No release notes entries required.
(x) Release notes entries required with the following suggested text: