Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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:
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
Attachments
Attachments
Issue Links
- is depended upon by
-
HIVE-10924 add support for MERGE statement
- Resolved
- relates to
-
HIVE-16073 Fix partition column check during runtime filtering
- Resolved
- supercedes
-
HIVE-16001 add test for merge + runtime filtering
- Resolved