You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Michael Ho (JIRA)" <ji...@apache.org> on 2017/03/15 18:26:41 UTC

[jira] [Assigned] (IMPALA-3548) Prune runtime filters based on RUNTIME_FILTER_MODE in the frontend

     [ https://issues.apache.org/jira/browse/IMPALA-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Ho reassigned IMPALA-3548:
----------------------------------

    Assignee: Attila Jeges  (was: Dimitris Tsirogiannis)

> Prune runtime filters based on RUNTIME_FILTER_MODE in the frontend
> ------------------------------------------------------------------
>
>                 Key: IMPALA-3548
>                 URL: https://issues.apache.org/jira/browse/IMPALA-3548
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>    Affects Versions: impala 2.5.1
>            Reporter: Dimitris Tsirogiannis
>            Assignee: Attila Jeges
>            Priority: Minor
>              Labels: runtime-filters, usability
>
> Currently, the FE generates a number of runtime filters and assigns them to plan nodes without taking the value of RUNTIME_FILTER_MODE into account. In the backend, the filters are removed from the exec nodes based on the target node types (local or remote) and the value of the RUNTIME_FILTER_MODE option. This may cause some confusion to users because they may see runtime filters in the output of explain that aren't applied when the query is executed. This operation should be performed in the FE.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)