[
https://issues.apache.org/jira/browse/HIVE-16604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16213771#comment-16213771
]
Lefty Leverenz commented on HIVE-16604:
---------------------------------------
Doc note: This needs to be documented in the wiki.
I'm not sure where the general documentation belongs, but the ENFORCED keyword
belongs here:
* [DDL -- Keywords |
https://cwiki.apache.org/confluence/display/Hive/LanguageManual+DDL#LanguageManualDDL-Keywords,Non-reservedKeywordsandReservedKeywords]
Added a TODOC3.0 label.
> 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
> Labels: TODOC3.0
> Fix For: 3.0.0
>
> Attachments: HIVE-16604.patch
>
>
> 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.4.14#64029)
