asterixdb-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Taewoo Kim (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:41:18 GMT

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

Taewoo Kim commented on ASTERIXDB-1326:
---------------------------------------

Conclusion: Let the IntroduceProjectsRule handle the removal of RIDs. 

> 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