You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2017/05/08 11:03:04 UTC

[jira] [Created] (HIVE-16604) Use [NOT] ENFORCED for column constraint characteristics

Jesus Camacho Rodriguez created HIVE-16604:
----------------------------------------------

             Summary: Use [NOT] ENFORCED for column constraint characteristics
                 Key: HIVE-16604
                 URL: https://issues.apache.org/jira/browse/HIVE-16604
             Project: Hive
          Issue Type: Improvement
    Affects Versions: 3.0.0
            Reporter: Carter Shanklin
            Assignee: Jesus Camacho Rodriguez


From HIVE-16575:

{quote}
SQL:2011 spec, 10.8, uses [ NOT ] ENFORCED for column constraint characteristics.
I think Oracle invented DISABLE and NORELY and maybe others have copied it over time.
A quick check I see DB2 uses the [ NOT ] ENFORCED. Teradata uses something else entirely.
Personally I think there are advantages to adopting the standard approach.
There is no standard approach for hinting the optimizer so we're on our own there.
{quote}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)