[
https://issues.apache.org/jira/browse/ASTERIXDB-1407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15254781#comment-15254781
]
ASF subversion and git services commented on ASTERIXDB-1407:
------------------------------------------------------------
Commit 68914a98532aa50eaf90b17fa4ab55ab32f7212c in incubator-asterixdb's branch
refs/heads/master from [~buyingyi]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=68914a9 ]
ASTERIXDB-1407: let the build branch to broadcast for NestedLoopJoin.
-Change the broadcast branch;
-Fix a bug in SuperActivityOperatorNodePushable;
-Fix jobbuilder to use a fixed location (within query) for operators
with "count=1" constraint;
-Fix OptimizerTest to generate the same directory structure for
actual files as expected files.
-Updates the test query plans.
Change-Id: I0988624406d2f7460f0ee5ac7b4829d81e48c652
Reviewed-on: https://asterix-gerrit.ics.uci.edu/828
Tested-by: Jenkins <[email protected]>
Reviewed-by: Jianfeng Jia <[email protected]>
> Let the build branch instead of the probe branch to broadcast for NLJ
> ---------------------------------------------------------------------
>
> Key: ASTERIXDB-1407
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1407
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Yingyi Bu
> Assignee: Yingyi Bu
>
> There are two motivations for that change:
> 1. Usually the build branch is smaller;
> 2. The data properties of the probe branch can still be maintained after a
> nested loop join but a broadcast will clear all data properties of a branch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
