Write metadata file #8
Merged
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.
Now when the table is created - the metadata file is written using
object_storeto the filesystem. Because we useobject_storeinterface, this could be easily extended to s3.In the
query_tablemethod we now successfully init the catalog using iceberg-rust library, that reads the metadata file.In the following PRs I will continue implementing querying functionality and whatever is missing in our catalog.
This is how I write the metadata file:
