[IMPALA-4252] Add RuntimeFilters for min/max at KuduScanNode

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Kudu_Impala
• Fix Version/s: Impala 2.11.0
• Component/s: Backend
• Labels: docs kudu performance runtime-filters
• Target Version: Kudu_Impala
• Assignee: Greg Rahn
• Reporter: Matthew Jacobs
• Created: 06/Oct/16 20:49
• Updated: 22/Mar/18 23:07
• Resolved: 17/Nov/17 21:37

Description

Kudu scans will benefit significantly from runtime filters. For now, we could generate min/max values instead of bloom filters to push to the KuduScanNode and, with support from the Kudu client (KUDU-1683), we could push them to Kudu during execution. At some point, it would be nice to push bloom filters to Kudu (IMPALA-3741), but that will require more work and should be a potential follow-up task to this.

Issue Links

• relates to: IMPALA-3430 Runtime filter : Extend runtime filter to support Min/Max values for HDFS scans
• relates to: IMPALA-3741 Push bloom filters to Kudu scanners