You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 supportsadd_constrant
, not arbitrary custom metadata. Becauseadd_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 addedcustom_metadata
inwrite_deltalake
, as people can usemerge
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 inwrite_deltalake
, so it could be done as one atomic transaction, when applicable, rather than having to do a write, then an alter.The text was updated successfully, but these errors were encountered: