[jira] [Updated] (SPARK-18594) Name Validation of Databases/Tables
[ https://issues.apache.org/jira/browse/SPARK-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dongjoon Hyun updated SPARK-18594: -- Fix Version/s: 2.1.0 > Name Validation of Databases/Tables > --- > > Key: SPARK-18594 > URL: https://issues.apache.org/jira/browse/SPARK-18594 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.0.2 >Reporter: Xiao Li >Assignee: Xiao Li > Fix For: 2.1.0 > > > Currently, the name validation checks are limited to table creation. It is > enfored by Analyzer rule: `PreWriteCheck`. > However, table renaming and database creation have the same issues. It makes > more sense to do the checks in `SessionCatalog`. -- This message was sent by Atlassian JIRA (v6.4.14#64029) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
[jira] [Updated] (SPARK-18594) Name Validation of Databases/Tables
[ https://issues.apache.org/jira/browse/SPARK-18594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xiao Li updated SPARK-18594: Target Version/s: 2.1.0 > Name Validation of Databases/Tables > --- > > Key: SPARK-18594 > URL: https://issues.apache.org/jira/browse/SPARK-18594 > Project: Spark > Issue Type: Bug > Components: SQL >Affects Versions: 2.0.2 >Reporter: Xiao Li > > Currently, the name validation checks are limited to table creation. It is > enfored by Analyzer rule: `PreWriteCheck`. > However, table renaming and database creation have the same issues. It makes > more sense to do the checks in `SessionCatalog`. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org
