You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (Jira)" <ji...@apache.org> on 2020/01/27 22:02:00 UTC
[jira] [Created] (IMPALA-9333) Potential runtime filter
optimisations
Tim Armstrong created IMPALA-9333:
-------------------------------------
Summary: Potential runtime filter optimisations
Key: IMPALA-9333
URL: https://issues.apache.org/jira/browse/IMPALA-9333
Project: IMPALA
Issue Type: Improvement
Components: Backend
Reporter: Tim Armstrong
Following on from IMPALA-4400, some miscellaneous optimisations are possible. Having a shared RuntimeFilterBank between all fragments on a backend allows some further optimizations to reduce the number of broadcast join filters sent over the network, by considering cross-fragment filters on the same backend as local filters:
# Produce a local filter on any backend with a destination fragment
# Only produce one local filter per backend (although, this would be made redundant by IMPALA-4224 - sharing broadcast join hash tables).
# Don't produce a global filter if all targets can be satisfied with local producers.
This work was deferred from the IMPALA-4400 change because it provides only incremental performance benefits. It's unclear if the benefit is significant.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)