Mailing-List: contact issues-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Thu, 2 Jun 2016 10:11:59 +0000 (UTC)
From: "Jesus Camacho Rodriguez (JIRA)" <jira@apache.org>
To: issues@hive.apache.org
Message-ID: <JIRA.12939875.1455730513000.13189.1464862319453@Atlassian.JIRA>
In-Reply-To: <JIRA.12939875.1455730513000@Atlassian.JIRA>
References: <JIRA.12939875.1455730513000@Atlassian.JIRA> <JIRA.12939875.1455730513090@arcas>
Subject: [jira] [Updated] (HIVE-13076) Implement FK/PK "rely novalidate"
 constraints for better CBO
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 10:12:01 -0000


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

Jesus Camacho Rodriguez updated HIVE-13076:
-------------------------------------------
    Fix Version/s:     (was: 2.1.0)

> 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
>         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)