[IMPALA-3874] Predicates are not always pushed to Kudu

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: Impala 2.6.0
• Fix Version/s: Kudu_Impala, Impala 2.8.0
• Component/s: Frontend
• Labels: kudu performance
• Target Version: Kudu_Impala
• Assignee: Matthew Jacobs
• Reporter: Dimitris Tsirogiannis
• Created: 18/Jul/16 23:57
• Updated: 12/Sep/16 22:39
• Resolved: 08/Sep/16 14:33

Description

Predicates in some cases do not seem to be pushed to Kudu and are executed at the Impala scan node instead. Example from the TPC-H Q6:

# Q6 - Forecasting Revenue Change Query
select
 round(sum(l_extendedprice * l_discount), 2) as revenue
from
  tpch_kudu.lineitem
where
  l_shipdate >= '1994-01-01'
  and l_shipdate < '1995-01-01'
  and l_discount between 0.05 and 0.07
  and l_quantity < 24
---- PLAN
01:AGGREGATE [FINALIZE]
|  output: sum(l_extendedprice * l_discount)
|
00:SCAN KUDU [tpch_kudu.lineitem]
   *predicates: l_quantity < 24, l_shipdate < '1995-01-01'*
   kudu predicates: l_discount >= 0.05, l_discount <= 0.07, l_shipdate >= '1994-01-01'

Issue Links

• is blocked by: IMPALA-3481 Kudu Connector: use new Scan Token API