[
https://issues.apache.org/jira/browse/IMPALA-9125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975724#comment-16975724
]
ASF subversion and git services commented on IMPALA-9125:
---------------------------------------------------------
Commit 2c2df0bcf0fbc77ba1244b6700deebb834355086 in impala's branch
refs/heads/master from Tim Armstrong
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=2c2df0b ]
IMPALA-9125: generalize finding DataSink from other fragment
This is a minor refactor that makes the existing mechanism
for finding PlanRootSink more general:
* Status-returning API to reduce boilerplate in caller.
* Avoid storing PlanRootSink as a member - this doesn't scale
nicely to multiple subclasses. Instead use an accessor method.
Change-Id: I3c91cadf9ecfde9cc3235bd71412ba10ee37bc4e
Reviewed-on: http://gerrit.cloudera.org:8080/14710
Reviewed-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>
> Add general mechanism to find DataSink from other fragments
> -----------------------------------------------------------
>
> Key: IMPALA-9125
> URL: https://issues.apache.org/jira/browse/IMPALA-9125
> Project: IMPALA
> Issue Type: Sub-task
> Components: Backend
> Reporter: Tim Armstrong
> Assignee: Tim Armstrong
> Priority: Major
>
> As a precursor to IMPALA-4224, we should add a mechanism for an finstance to
> discover the join build sink from another finstance.
> We already have a related single-purpose mechanism in the coordinator to find
> PlanRootSink. We should generalise this to allow looking up the sink of any
> other finstance and move it into QueryState
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
