Add FileMetadata table and RowMetadataRegistry
#2
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.
This PR is mostly a port of internal code from Polygon.io, with some new additions to make it generic so that users with custom
TableProviderimplementations can use it effectively.FileMetadatais a customTableProviderthat exposes object store metadata through SQL. It implementsRowMetadataSource, a trait that provides metadata which will be used in incremental view maintenance (which is not included in this PR).In order for these components to accommodate custom table types, we have added a
ListingTableLiketrait that abstracts away the essential features of a Hive-partitioned table. Users must register their custom table types using theregister_listing_tableAPI if they expect this crate to detect and work properly with these tables.This PR ended up quite a bit bigger than I expected, unfortunately. Most of the length comes from the
FileMetadatatable provider, which implements filter pushdown.