Uh oh!
There was an error while loading. Please reload this page.
[SPARK-17166] [SQL] Store Table Properties in CTAS that is Converted to Data Source Tables - #14727
[SPARK-17166] [SQL] Store Table Properties in CTAS that is Converted to Data Source Tables#14727gatorsmile wants to merge 1 commit into
Conversation
gatorsmile
commented
Aug 20, 2016
cc @cloud-fan@yhuai This is what we discussed in another PR. Could you please review whether this is a right fix? Thanks! |
SparkQA
commented
Aug 20, 2016
Test build #64125 has finished for PR 14727 at commit
|
| assert(tableDesc.properties.get("prop1").isEmpty) | ||
| assert(tableDesc.properties.get("prop2").isEmpty) | ||
| assert(tableDesc.storage.properties.get("prop1") == Option("c")) | ||
| assert(tableDesc.storage.properties.get("prop2") == Option("d")) |
There was a problem hiding this comment.
is this what we want? Why do the table properties in Hive serde table should go to storage properties in data source table?
Ideally data source table should have data source options(storage properties) and table properties. Currently we don't support specifying table properties for data source tables, but it doesn't mean we will never do it. I think we can do it when unify the CREATE TABLE syntax.
There was a problem hiding this comment.
uh, agree! Let me close this PR. Thanks!
What changes were proposed in this pull request?
CTAS lost table properties after conversion to data source tables. For example,
The output of
DESC FORMATTED tdoes not have the related properties.After the fix, the properties specified by users are stored as serde properties, since the table properties are used for storing table schemas and system generated properties.
How was this patch tested?
Added a test case.