You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sunitha Kambhampati (JIRA)" <ji...@apache.org> on 2017/09/19 19:24:00 UTC

[jira] [Created] (SPARK-22064) Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command

Sunitha Kambhampati created SPARK-22064:
-------------------------------------------

             Summary:  Add support for VALIDATE option to ALTER TABLE ADD CONSTRAINT command
                 Key: SPARK-22064
                 URL: https://issues.apache.org/jira/browse/SPARK-22064
             Project: Spark
          Issue Type: Sub-task
          Components: SQL
    Affects Versions: 3.0.0
            Reporter: Sunitha Kambhampati


As part of the Informational Referential Integrity constraints feature, in SPARK-21784, the ALTER TABLE ADD CONSTRAINT DDL is added.  
{quote}ALTER TABLE [db_name.]table_name ADD [CONSTRAINT constraintName]
  (PRIMARY KEY (col_names) |
  FOREIGN KEY (col_names) REFERENCES [db_name.]table_name [(col_names)])
  [VALIDATE | NOVALIDATE] [RELY | NORELY]
{quote}

In this JIRA, we will add support to add a constraint with the VALIDATE option and perform the validation for the constraint. We will validate the constraint by running specific internal SQL statements to check if the data conforms to the constraint. 

	E.g  {quote}ALTER TABLE employee ADD CONSTRAINT pk1 PRIMARY KEY (empno) VALIDATE RELY{quote}
  
The high level details are in the [^InformationalRIConstraints.doc] in Section 4.2.3 and Section 4.5



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org