asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (ASTERIXDB-1407) Let the build branch instead of the probe branch to broadcast for NLJ
Date Fri, 22 Apr 2016 22:04:12 GMT


ASF subversion and git services commented on ASTERIXDB-1407:

Commit 68914a98532aa50eaf90b17fa4ab55ab32f7212c in incubator-asterixdb's branch refs/heads/master
from [~buyingyi]
[;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
Tested-by: Jenkins <>
Reviewed-by: Jianfeng Jia <>

> Let the build branch instead of the probe branch to broadcast for NLJ
> ---------------------------------------------------------------------
>                 Key: ASTERIXDB-1407
>                 URL:
>             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

View raw message