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 2019/12/06 03:17:00 UTC

[jira] [Resolved] (IMPALA-9126) Cleanly separate build and probe state in hash join node

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

Tim Armstrong resolved IMPALA-9126.
-----------------------------------
    Fix Version/s: Impala 3.4.0
       Resolution: Fixed

> Cleanly separate build and probe state in hash join node
> --------------------------------------------------------
>
>                 Key: IMPALA-9126
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9126
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: multithreading
>             Fix For: Impala 3.4.0
>
>
> As a precursor to IMPALA-4224, we should clean up the hash join implementation so that the build and probe state is better separated. The builder should not deal with probe side data structures (like the probe streams that it allocates) and all accesses to the build-side data structures should go through as narrow APIs as possible.
> The nested loop join is already pretty clean.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)