[ 
https://issues.apache.org/jira/browse/ASTERIXDB-1020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15075717#comment-15075717
 ] 

ASF subversion and git services commented on ASTERIXDB-1020:
------------------------------------------------------------

Commit 7dd4799235619eb8bba35b6aed65b8b4d8b6f113 in 
incubator-asterixdb-hyracks's branch refs/heads/master from [~buyingyi]
[ 
https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb-hyracks.git;h=7dd4799
 ]

Fix for ASTERIXDB-1018, ASTERIXDB-1017, ASTERIXDB-1019,
ASTERIXDB-1020, ASTERIXDB-1029, ASTERIXDB-1030, ASTERIXDB-1034:

1. Let the keys of introduced nested group-bys (group-bys in a subplan) be only 
the
variables that are produced in the subplan;

2. In PushSelectIntoJoinRule, push independent operators (e.g., a 
current-datetime() call)
into the first branch from which the join condition refers some variables.

3. In SimpleUnnestToJoinRule, move the boundary between the two join branches 
of a added join
which results from pipelined datascans to be below operators that doesn't use 
any variables
(e.g., a current-datetime() call), therefore potentially, the upper (left) join 
branch
can be rewritten to index lookups.

Change-Id: I18cfa3875d676f71b26e91433ff101a7e725c890
Reviewed-on: https://asterix-gerrit.ics.uci.edu/488
Tested-by: Jenkins <[email protected]>
Reviewed-by: Yingyi Bu <[email protected]>


> Rewrite rule fails on visitAssignOperator
> -----------------------------------------
>
>                 Key: ASTERIXDB-1020
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1020
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: AsterixDB, Optimizer
>            Reporter: asterixdb-importer
>            Assignee: Yingyi Bu
>
> Rewrite rule fails on visitAssignOperator



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to