hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesus Camacho Rodriguez (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-17054) Expose SQL database constraints to Calcite
Date Thu, 19 Oct 2017 18:36:00 GMT

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

Jesus Camacho Rodriguez updated HIVE-17054:
-------------------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Pushed to master, thanks for reviewing [~ashutoshc]!

> 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
>
>         Attachments: HIVE-17054.patch
>
>
> 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)

Mime
View raw message