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

Posted to issues@hive.apache.org by "Hari Sankar Sivarama Subramaniyan (JIRA)" <ji...@apache.org> on 2016/05/11 21:55:12 UTC

[jira] [Updated] (HIVE-13076) Implement FK/PK "rely novalidate" constraints for better CBO

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

Hari Sankar Sivarama Subramaniyan updated HIVE-13076:
-----------------------------------------------------
    Attachment: AddingPKFKconstraints.pdf

> Implement FK/PK "rely novalidate" constraints for better CBO
> ------------------------------------------------------------
>
>                 Key: HIVE-13076
>                 URL: https://issues.apache.org/jira/browse/HIVE-13076
>             Project: Hive
>          Issue Type: Improvement
>          Components: CBO, Logical Optimizer
>            Reporter: Ruslan Dautkhanov
>            Assignee: Hari Sankar Sivarama Subramaniyan
>             Fix For: 2.1.0
>
>         Attachments: AddingPKFKconstraints.pdf
>
>
> Oracle has "RELY NOVALIDATE" option for constraints.. Could be easier for Hive to start with something like that for PK/FK constraints. So CBO has more information for optimizations. It does not have to actually check if that constraint is relationship is true; it can just "rely" on that constraint.. 
> https://docs.oracle.com/database/121/SQLRF/clauses002.htm#sthref2289
> So it would be helpful with join cardinality estimates, and with cases like this - https://issues.apache.org/jira/browse/HIVE-13019



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)