hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HIVE-24087) FK side join elimination in presence of PK-FK constraint
Date Fri, 28 Aug 2020 17:07:02 GMT

     [ https://issues.apache.org/jira/browse/HIVE-24087?focusedWorklogId=475907&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-475907
]

ASF GitHub Bot logged work on HIVE-24087:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 28/Aug/20 17:06
            Start Date: 28/Aug/20 17:06
    Worklog Time Spent: 10m 
      Work Description: vineetgarg02 commented on pull request #1440:
URL: https://github.com/apache/hive/pull/1440#issuecomment-682920806


   @jcamachor Thanks for the suggestions. I will add all three tests (and yes all of these
cases are expected to trigger the rewrite)


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 475907)
    Time Spent: 50m  (was: 40m)

> FK side join elimination in presence of PK-FK constraint
> --------------------------------------------------------
>
>                 Key: HIVE-24087
>                 URL: https://issues.apache.org/jira/browse/HIVE-24087
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Planning
>            Reporter: Vineet Garg
>            Assignee: Vineet Garg
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> If there is PK-FK join FK join could be eliminated by removing FK side if following conditions
are met
> * There is no row filtering on FK side.
> * No columns from FK side is required after JOIN.
> * FK join columns are guranteed to be unique (have group by)
> * FK join columns are guranteed to be NOT NULL (either IS NOT NULL filter or constraint)
> *Example*
> {code:sql}
> EXPLAIN 
> SELECT customer_removal_n0.*
> FROM customer_removal_n0
>     JOIN
>     (SELECT lo_custkey
>     FROM lineorder_removal_n0
>     WHERE lo_custkey IS NOT NULL
>     GROUP BY lo_custkey) fkSide ON fkSide.lo_custkey = customer_removal_n0.c_custkey;
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message