[
https://issues.apache.org/jira/browse/HIVE-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16103600#comment-16103600
]
Jesus Camacho Rodriguez commented on HIVE-17039:
------------------------------------------------
[~sershe], currently they are not, but we already have different options to
enforce them vs rely on them for optimization purposes (other RDBMS can make
this distinction too).
> Implement optimization rewritings that rely on database SQL constraints
> -----------------------------------------------------------------------
>
> Key: HIVE-17039
> URL: https://issues.apache.org/jira/browse/HIVE-17039
> Project: Hive
> Issue Type: New Feature
> Components: Logical Optimizer
> Affects Versions: 3.0.0
> Reporter: Jesus Camacho Rodriguez
>
> Hive already has support to declare multiple SQL constraints (PRIMARY KEY,
> FOREIGN KEY, UNIQUE, and NOT NULL). Although these constraints cannot be
> currently enforced on the data, they can be made available to the optimizer
> by using the 'RELY' keyword.
> This ticket is an umbrella for all the rewriting optimizations based on SQL
> constraints that we will be including in Hive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
