You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2020/01/16 13:50:00 UTC
[jira] [Resolved] (SPARK-30507) TableCalalog reserved properties
shoudn't be changed with options or tblpropeties
[ https://issues.apache.org/jira/browse/SPARK-30507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-30507.
---------------------------------
Fix Version/s: 3.0.0
Resolution: Fixed
Issue resolved by pull request 27197
[https://github.com/apache/spark/pull/27197]
> TableCalalog reserved properties shoudn't be changed with options or tblpropeties
> ---------------------------------------------------------------------------------
>
> Key: SPARK-30507
> URL: https://issues.apache.org/jira/browse/SPARK-30507
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Kent Yao
> Assignee: Kent Yao
> Priority: Major
> Fix For: 3.0.0
>
>
> Instead of using `OPTIONS (k='v')` or TBLPROPERTIES (k='v'), if k is a reserved TableCatalog property, we should use its specific syntax to add/modify/delete it.
> e.g. provider is a reserved property, we should use the USING clause to specify it, and should not allow ALTER TABLE ... UNSET TBLPROPERTIES('provider') to delete it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org