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
Can I safely store custom metadata as additional rows in the ducklake_metadata table? The my_ducklake.set_option() function (docs: Configuration) checks if the key is one of the known keys. But, if I insert additional data directly into the ducklake_metadata table, they are returned by the my_ducklake.options() function without issue.
I'd basically like to store additional metadata about my DuckLake catalogs for custom use.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Can I safely store custom metadata as additional rows in the
ducklake_metadatatable? Themy_ducklake.set_option()function (docs: Configuration) checks if the key is one of the known keys. But, if I insert additional data directly into theducklake_metadatatable, they are returned by themy_ducklake.options()function without issue.I'd basically like to store additional metadata about my DuckLake catalogs for custom use.
Beta Was this translation helpful? Give feedback.
All reactions