You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Abdullah Alamoudi (JIRA)" <ji...@apache.org> on 2017/09/03 17:49:00 UTC
[jira] [Commented] (ASTERIXDB-1647) Some logical operators'
implementations of isMap doesn't match their behavior
[ https://issues.apache.org/jira/browse/ASTERIXDB-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151881#comment-16151881 ]
Abdullah Alamoudi commented on ASTERIXDB-1647:
----------------------------------------------
Current implementations of isMap() returns
true:
-Assign
-AbstractReplicateOperator
-AbstractUnnestOperator
-ExchangeOperator
-InsertDeleteUpsertOperator
-LimitOperator
-ProjectOperator
-SelectOperator
false:
-Order
-Aggregate
-RunningAggregate
-AbstractBinaryJoin
-AbstractOperatorWithNestedPlans
-DataSourceScanOperator
-DistinctOperator
-DistributeResultOperator
-EmptyTupleSourceOperator
-IndexInsertDeleteUpsertOperator
-IntersectOperator
-MaterializeOperator
-NestedTupleSourceOperator
-ScriptOperator
-SinkOperator
-TokenizeOperator
-UnionAllOperator
-WriteOperator
-WriteResultOperator
Clearly, we have a problem in at least two of:
-IndexInsertDeleteUpsertOperator
-TokenizeOperator
-InsertDeleteUpsertOperator
-AbstractUnnestOperator
> Some logical operators' implementations of isMap doesn't match their behavior
> -----------------------------------------------------------------------------
>
> Key: ASTERIXDB-1647
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1647
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Abdullah Alamoudi
> Assignee: Abdullah Alamoudi
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)