You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Jesus Camacho Rodriguez (Jira)" <ji...@apache.org> on 2019/09/15 19:11:00 UTC

[jira] [Resolved] (HIVE-17039) Implement optimization rewritings that rely on database SQL constraints

     [ https://issues.apache.org/jira/browse/HIVE-17039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesus Camacho Rodriguez resolved HIVE-17039.
--------------------------------------------
    Resolution: Done

> 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
>            Priority: Major
>
> 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
(v8.3.2#803003)