[jira] [Commented] (KUDU-1683) Kudu client support for pushing runtime min/max filters

["Grant Henke (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17124326#comment-17124326 ] 

Grant Henke commented on KUDU-1683:
-----------------------------------

From some recent discussions it looks like the ability to add filters after a scan has started has a significantly reduced impact based on:
* In Impala/Parquet we have seen limited cases where it's beneficial to start the scan before filters arrive, and add them later. In the majority of cases it makes sense to wait for them to arrive instead (waiting up to 60s for example)
* With IMPALA-9792/KUDU-2437 there will be more smaller scans and we can add the filters to the new scans as when they arrive.

> Kudu client support for pushing runtime min/max filters
> -------------------------------------------------------
>
>                 Key: KUDU-1683
>                 URL: https://issues.apache.org/jira/browse/KUDU-1683
>             Project: Kudu
>          Issue Type: New Feature
>          Components: client, perf
>    Affects Versions: 1.0.0
>            Reporter: Matthew Jacobs
>            Priority: Major
>              Labels: impala, roadmap-candidate
>
> Impala would like to generate runtime min/max filters to be pushed to Kudu, at least for scan tokens that haven't been opened yet.
> https://issues.cloudera.org/browse/IMPALA-4252



--
This message was sent by Atlassian Jira
(v8.3.4#803005)