[
https://issues.apache.org/jira/browse/IMPALA-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-6145.
-----------------------------------
Resolution: Won't Fix
> Assign runtime filter ids lazily
> --------------------------------
>
> Key: IMPALA-6145
> URL: https://issues.apache.org/jira/browse/IMPALA-6145
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 2.11.0
> Reporter: Thomas Tauber-Marshall
> Priority: Minor
>
> Currently, when generating runtime filters we iterate over the plan tree,
> create a filter for each equi join predicate of each hash join node, and
> assign them ascending ids.
> Not all of the created filters always end up assigned to a target scan node,
> and those that aren't assigned are left out of the plan, resulting in gaps in
> the sequence of filter ids in the explain output, which could be confusing to
> users.
> It would be better to assign filter ids only to filters that end up in the
> final plan, so that the max filter id in the plan is equal to the total
> number of filters in the plan.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
