[
https://issues.apache.org/jira/browse/HIVE-13350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279381#comment-15279381
]
Hari Sankar Sivarama Subramaniyan commented on HIVE-13350:
----------------------------------------------------------
Is adding constraint with different name allowed (keeping its other properties
intact) ?
It is allowed as of now. I have not added this check since this will require
metastore to run an extra query against the db while trying to insert the
constraint. That being said, it might be good to have this check in future
based on how badly this feature is misused by the end user.
I will upload the -ve test cases in the next patch.
Thanks
Hari
> Support Alter commands for Rely/NoRely novalidate for PK/FK constraints
> ------------------------------------------------------------------------
>
> Key: HIVE-13350
> URL: https://issues.apache.org/jira/browse/HIVE-13350
> Project: Hive
> Issue Type: Sub-task
> Components: CBO, Logical Optimizer
> Reporter: Hari Sankar Sivarama Subramaniyan
> Assignee: Hari Sankar Sivarama Subramaniyan
> Attachments: HIVE-13350.1.patch
>
>
> Support commands like :
> ALTER TABLE table2 ADD CONSTRAINT pkt2 primary key (a) disable novalidate;
> ALTER TABLE table3 ADD CONSTRAINT fk1 FOREIGN KEY ( x ) REFERENCES table2(a)
> DISABLE NOVALIDATE RELY;
> ALTER TABLE table6 ADD CONSTRAINT fk4 FOREIGN KEY ( y ) REFERENCES table1(a)
> DISABLE NOVALIDATE;
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
