Skip to content
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 custom table properties via TableAlterer and write/merge #2022

Closed
echai58 opened this issue Jan 3, 2024 · 2 comments
Closed

Support custom table properties via TableAlterer and write/merge #2022

echai58 opened this issue Jan 3, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@echai58
Copy link

echai58 commented Jan 3, 2024

Description

Delta Lake via spark supports storing custom metadata as a table property via both CREATE and ALTER commands. Currently, delta-rs only supports custom configuration on table creation. TableAlterer exists, but it only supports add_constrant, not arbitrary custom metadata. Because add_constraint exists, I imagine there exists the framework already to support this and it would not be a difficult addition.

Also, merge should allow for fields like the newly added custom_metadata in write_deltalake, as people can use merge as an upsert-style write.

Use Case
There are many scenarios where we'd want to support table-level metadata that can be accessed via DeltaTable.metadata(), and they should be able to be altered in the future, not just on table creation.

Ideally, this would also allow for the configuration field to be used in write_deltalake, so it could be done as one atomic transaction, when applicable, rather than having to do a write, then an alter.

@echai58 echai58 added the enhancement New feature or request label Jan 3, 2024
@ion-elgreco
Copy link
Collaborator

ion-elgreco commented Jan 3, 2024

Yes this is on the backlog, we are tracking it here: #1909

I will take a look at exposing custom_metadata in merge, can you create a separate issue for that? 😄

@ion-elgreco ion-elgreco closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2024
@echai58
Copy link
Author

echai58 commented Jan 4, 2024

Yes this is on the backlog, we are tracking it here: #1909

I will take a look at exposing custom_metadata in merge, can you create a separate issue for that? 😄

@ion-elgreco Great, thanks! Here's a new issue for exposing custom_metadata in merge: #2031

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants