-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Writing Iceberg metadata #21
Comments
is there any ETA for this? |
It's on our shortlist, but we don't have a concrete ETA yet. The challenges are:
|
@umeshkacha |
Sounds good Zhou. Thanks for the update. Any ETA?
Thanks,
Umesh
…On Sat, Jan 18, 2025 at 1:05 AM Zhou Sun ***@***.***> wrote:
@umeshkacha <https://github.com/umeshkacha>
Another big difference is Iceberg usually requires a catalog to work,
which makes the setup a lot more complex for regular postgres user.
This is changing with S3 Table Bucket
<https://www.mooncake.dev/blog/s3tables>, I am working on a prototype
with S3 Table Bucket.
—
Reply to this email directly, view it on GitHub
<#21 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAE45HS3XTSP5PTXEKJKTL32LFLRTAVCNFSM6AAAAABRN7EV26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJZGA3DGMRQHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What feature are you requesting?
Currently pg_mooncake is wring delta metadata to the object store. But it would be ideal to also write iceberg version.
Why are you requesting this feature?
Fit better into the iceberg ecosystem.
What is your proposed implementation for this feature?
Implement the corresponding functions for iceberg, with same semantics.
Catalog support for iceberg is more important than delta, but for MVP it is fine to just write to filesystem.
The text was updated successfully, but these errors were encountered: