[
https://issues.apache.org/jira/browse/ASTERIXDB-1291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15140041#comment-15140041
]
ASF subversion and git services commented on ASTERIXDB-1291:
------------------------------------------------------------
Commit d960fd355813c6496b5fed2081e018e59bd216d9 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=d960fd3
]
Fix for ASTERIXDB-1291: deals with the case that a NTS' data source operator
has been deep copied.
Change-Id: Ie3efa74e38bbfa9eee4a20e4a9cf6fc2a5840973
Reviewed-on: https://asterix-gerrit.ics.uci.edu/622
Tested-by: Jenkins <[email protected]>
Reviewed-by: Wenhai Li <[email protected]>
Reviewed-by: Taewoo Kim <[email protected]>
> LogicalOperatorDeepCopyWithNewVariablesVisitor needs to deals with
> NestedTupleSource properly
> ---------------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-1291
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1291
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Yingyi Bu
> Assignee: Yingyi Bu
>
> DeepCopyWithVariableMappingVisitor needs to deals with NestedTupleSource
> properly, according to whether the datasource reference operator is part of
> the deep copy:
> case 1: it is not, then in the copy of NTS, the data source reference should
> point to the original data source reference;
> case 2: it is, then in the copy of NTS, the data source reference should
> point to the copied instance of the original data source reference.
> In the current master, we only deal with case 1 but not case 2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
