Add Functionality to Read Table Metadata Path from Iceberg REST Catalog #92
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
# Conflicts: # test/sql/iceberg_catalog.test
# Conflicts: # .github/workflows/Rest.yml
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.
This PR introduces the ability to read the Iceberg table metadata path from an Iceberg REST catalog as discussed in #16. One example is the following query.
The IcebergSnapshot::GetMetaDataPath method has been updated to fetch the metadata location from the appropriate REST endpoint, as specified in the Iceberg REST Catalog Open API Spec. (
GET /v1/{prefix}/namespaces/{namespace}/tables/{table}in https://github.com/apache/iceberg/blob/main/open-api/rest-catalog-open-api.yaml).These changes are tested using the existing REST catalog setup.