[
https://issues.apache.org/jira/browse/IMPALA-9126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16979679#comment-16979679
]
ASF subversion and git services commented on IMPALA-9126:
---------------------------------------------------------
Commit abdd5ab7de8144b21ca320a9ad20565d543f01e6 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=abdd5ab ]
IMPALA-9126: part 1: hash join build partition cleanup
Clarify some invariants (e.g. which join modes actually
require build partition data to be attached to row batches).
Move some logic for maintenance of the hash partitions to
the builder.
Testing:
Ran exhaustive tests. We should already have adequate coverage for
spilling and non-spilling hash joins.
Change-Id: Ife8d0fa5dd14c7d3f3d726dd38c07d8cbceabadb
Reviewed-on: http://gerrit.cloudera.org:8080/14632
Reviewed-by: Impala Public Jenkins <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> 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: Sub-task
> Components: Backend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
