[
https://issues.apache.org/jira/browse/IMPALA-14275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Smith resolved IMPALA-14275.
------------------------------------
Fix Version/s: Impala 5.0.0
Resolution: Fixed
> Tuple cache needs to differentiate between consumed vs produced runtime
> filters
> -------------------------------------------------------------------------------
>
> Key: IMPALA-14275
> URL: https://issues.apache.org/jira/browse/IMPALA-14275
> Project: IMPALA
> Issue Type: Bug
> Components: Frontend
> Affects Versions: Impala 5.0.0
> Reporter: Joe McDonnell
> Assignee: Joe McDonnell
> Priority: Major
> Fix For: Impala 5.0.0
>
>
> The tuple cache needs to include information about consumed runtime filters
> (e.g. a scan node receiving a runtime filter) to have a correct cache key.
> The code is currently considering all runtime filters whether they are
> produced or consumed. A hash join that produces a runtime filter will include
> that in the hash. We should only include this for consumed runtime filters.
> This only applies to mt_dop=0, because with mt_dop > 0 the runtime filter is
> produced by the join builder fragment, which doesn't enter into the
> calculations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
