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 2017/10/19 00:50:00 UTC

[jira] [Work started] (HIVE-17054) Expose SQL database constraints to Calcite

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

Work on HIVE-17054 started by Jesus Camacho Rodriguez.
------------------------------------------------------
> Expose SQL database constraints to Calcite
> ------------------------------------------
>
>                 Key: HIVE-17054
>                 URL: https://issues.apache.org/jira/browse/HIVE-17054
>             Project: Hive
>          Issue Type: Improvement
>          Components: Logical Optimizer
>    Affects Versions: 3.0.0
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Jesus Camacho Rodriguez
>             Fix For: 3.0.0
>
>
> 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.
> Currently, even when they are declared with the RELY keyword, they are not exposed to Calcite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)