hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16154) Determine when dynamic runtime filtering should be disabled
Date Thu, 09 Mar 2017 11:35:37 GMT

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

Jason Dere updated HIVE-16154:
------------------------------
    Attachment: HIVE-16154.1.patch

Initial patch to compute benefit based on the selectivity of the semijoin attribute's ndv
vs the combined cardinality of the join key attributes from both sides of the join, and the
table size of the table being filtered.

> Determine when dynamic runtime filtering should be disabled
> -----------------------------------------------------------
>
>                 Key: HIVE-16154
>                 URL: https://issues.apache.org/jira/browse/HIVE-16154
>             Project: Hive
>          Issue Type: Bug
>          Components: Query Planning
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>         Attachments: HIVE-16154.1.patch
>
>
> Currently dynamic min/max/bloom optimization is always enabled. However there are times
where it may not be beneficial, such as if the semijoin has a PK-FK relation and there are
no filters on the semijoin table. Try to devise a way to do a cost/benefit calculation to
see if there is enough benefit to adding the runtime filter.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message