[ https://issues.apache.org/jira/browse/HIVE-16154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lefty Leverenz updated HIVE-16154: ---------------------------------- Labels: TODOC2.2 (was: ) > 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 > Labels: TODOC2.2 > Fix For: 2.2.0 > > Attachments: HIVE-16154.1.patch, HIVE-16154.2.patch, > HIVE-16154.3.patch, HIVE-16154.4.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)