Suresh Thalamati created SPARK-21823:
----------------------------------------

             Summary: ALTER TABLE table statements  such as RENAME and CHANGE 
columns should  raise  error if there are any dependent constraints. 
                 Key: SPARK-21823
                 URL: https://issues.apache.org/jira/browse/SPARK-21823
             Project: Spark
          Issue Type: Sub-task
          Components: SQL
    Affects Versions: 3.0.0
            Reporter: Suresh Thalamati


Following ALTER TABLE DDL statements will impact  the  informational 
constraints defined on a table:

{code:sql}
ALTER TABLE name RENAME TO new_name
ALTER TABLE name CHANGE column_name new_name new_type
{code}

Spark SQL should raise errors if there are 
 informational constraints defined 
on the columns  affected by the ALTER  and let the user drop constraints before 
proceeding with the DDL. In the future we can enhance the  ALTER  to 
automatically fix up the constraint definition in the catalog when possible, 
and not raise error

When spark adds support for DROP/REPLACE of columns they will impact 
informational constraints.
{code:sql}
ALTER TABLE name DROP [COLUMN] column_name
ALTER TABLE name REPLACE COLUMNS (col_spec[, col_spec ...])
{code}




--
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

Reply via email to