[ https://issues.apache.org/jira/browse/HIVE-16022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15888524#comment-15888524 ]
Deepak Jaiswal commented on HIVE-16022: --------------------------------------- As Jason mentioned, the check was added because semijoin reduction does not work properly with partition column, the reason being, it is not a real column but a logical one. The logic expects a real column to compute min and max. Aslo, there can never be parallel DPP and semijoin branches by design as they are created in if ...else if... block. > BloomFilter check not showing up in MERGE statement queries > ----------------------------------------------------------- > > Key: HIVE-16022 > URL: https://issues.apache.org/jira/browse/HIVE-16022 > Project: Hive > Issue Type: Bug > Components: Query Planning > Reporter: Jason Dere > Assignee: Jason Dere > Fix For: 2.2.0 > > Attachments: HIVE-16022.1.patch, HIVE-16022.2.patch, > HIVE-16022.3.patch, HIVE-16022.4.patch > > > Running explain on a MERGE statement with runtime filtering enabled, I see > the min/max being applied on the large table, but not the bloom filter check: > {noformat} > explain merge into acidTbl as t using nonAcidOrcTbl s ON t.a = s.a > WHEN MATCHED AND s.a > 8 THEN DELETE > WHEN MATCHED THEN UPDATE SET b = 7 > WHEN NOT MATCHED THEN INSERT VALUES(s.a, s.b) > ... > Map 1 > Map Operator Tree: > TableScan > alias: t > Statistics: Num rows: 1 Data size: 0 Basic stats: PARTIAL > Column stats: NONE > Filter Operator > predicate: a BETWEEN DynamicValue(RS_3_s_a_min) AND > DynamicValue(RS_3_s_a_max) (type: boolean) > Statistics: Num rows: 1 Data size: 0 Basic stats: PARTIAL > Column stats: NONE > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)