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

["Attila Jeges (JIRA)" <ji...@apache.org>]

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

Attila Jeges resolved IMPALA-3548.
----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.11.0

https://github.com/apache/incubator-impala/commit/00fd8388c37e1b3207dddf564463b7eeafe3f887

IMPALA-3548: Prune runtime filters based on query options in the FE
Currently, the FE generates a number of runtime filters and assigns
them to the single node plan without taking the value of
RUNTIME_FILTER_MODE and DISABLE_ROW_RUNTIME_FILTERING query options
into account.

The backend then removes filters from exec nodes, based on the
following rules:
1. If DISABLE_ROW_RUNTIME_FILTERING is set, filters are removed from
   the exec nodes that are marked as targets not bound by partition
   columns.

2. If RUNTIME_FILTER_MODE is set to LOCAL, filters are removed from
   the exec nodes that are marked as remote targets.

This may cause some confusion to users because they may see runtime
filters in the output of explain that are not applied when the query
is executed.

This change moves the logic of runtime filter pruning to the planner
in the FE. The runtime filter assignment is done on the distributed
plan and the above constraints are enforced there directly.

Change-Id: Id0f0b200e02442edcad8df3979f652d66c6e52eb
Reviewed-on: http://gerrit.cloudera.org:8080/7564
Tested-by: Impala Public Jenkins
Reviewed-by: Alex Behm <al...@cloudera.com>

> 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
>             Fix For: Impala 2.11.0
>
>
> 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.4.14#64029)