asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ASTERIXDB-1326) Left-outer-join on an external dataset doesn't work
Date Mon, 29 Feb 2016 16:39:18 GMT

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

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

Commit 06e06b052bebdf6a1841a72da37b876b081bf54d in incubator-asterixdb's branch refs/heads/master
from [~wangsaeu]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-asterixdb.git;h=06e06b0 ]

ASTERIXDB-1325, ASTERIXDB-1326: fixed leftouterjoin on an external dataset

 - Fixed the issue that optimizer ignores index_nl hint on an index on an external dataset.
 - Fixed the issue that index-nested-loop-leftouterjoin on an external dataset returns an
empty results.
 - Modified OptimizerTest to enable mockup HDFSCluster.
 - Added an optimizer test on an external dataset.

Change-Id: I91b2e57f0bd1beaa58dd28a84d8e08d308246b26
Reviewed-on: https://asterix-gerrit.ics.uci.edu/672
Reviewed-by: abdullah alamoudi <bamousaa@gmail.com>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>


> Left-outer-join on an external dataset doesn't work
> ---------------------------------------------------
>
>                 Key: ASTERIXDB-1326
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-1326
>             Project: Apache AsterixDB
>          Issue Type: Bug
>            Reporter: Taewoo Kim
>            Assignee: Taewoo Kim
>
> Left-outer-join on an external dataset generates empty results. For left-outer-join,
retainInput and retainNull are all set to true. When retainInput is set to true, in the inner
branch, what LookupAdapter does is that propagating all input variables except RIDs (two variables)
and additionally generate a record (when there is a matching) or a null (when there is no
matching). However, since the logical unnest-map operator does not filter RID information,
the Record Descriptor keeps the RID information. Thus, the next operator expects "all input
variables including RID + lookupAdapter output variable." However, what LookupAdapter generates
is "all input variables - RID + lookupAdapter output". 



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

Mime
View raw message