-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Cannot set metadata.description #299
Comments
Hmm, you are probably right. We should add DDL that lets you set the table description. |
I can actually add a comment to a table while creating a delta table. So maybe we can implement a fallback to table.comment if the metadata.description is not set |
This is probably because we don't yet really integrate with the metastore (this is coming soon #85), so you are just getting the default Spark behavior for create table. We could implement a fallback, but in general we try to keep the transaction log as the source of truth with the metastore only being a "symlink" to the table. Some users access the same table from multiple systems / metastores and it might be confusing if they diverge. |
@marmbrus is this something I can help you with? Seems like a small issue I could probably implement/fix myself. |
Yeah sure! The first question I would look at is if Spark has an extension point here that would allow us to intercept existing DDL to set the comment for a table. @brkyvz might know. |
With Spark 3.0, there is a new |
Hi, I'm trying to figure out how to set the description of a delta table. Table.comment is used for non-delta tables (https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/commands/DescribeDeltaDetailsCommandBase.scala#L126), but for delta tables it uses metadata.description (https://github.com/delta-io/delta/blob/master/src/main/scala/org/apache/spark/sql/delta/commands/DescribeDeltaDetailsCommandBase.scala#L170).
However, it seems impossible to set metadata.description. Or am I missing something?
The text was updated successfully, but these errors were encountered: