[
https://issues.apache.org/jira/browse/ASTERIXDB-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15394426#comment-15394426
]
Steven Jacobs commented on ASTERIXDB-1174:
------------------------------------------
This is actually a hard-coded problem. Unfortunately I don't have any queries
that I know of to produce the message, but I know where the codebase performs
the check. Unless there is some new guarantee that opMap will not be greater
than 1, the problem should still exist. It can be seen in
AbstractPhysicalOperator.buildPipelineWithProjection
> Allow for more complex nested plans
> -----------------------------------
>
> Key: ASTERIXDB-1174
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1174
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Steven Jacobs
> Assignee: Steven Jacobs
> Priority: Minor
>
> Currently, when nested plans get too complex (such as containing joins) we
> get a message such as:
> Attempting to construct a nested plan with 14 operator descriptors.
> Currently, nested plans can only consist in linear pipelines of Asterix micro
> operators. [AlgebricksException]
> It would be nice if we could allow such plans
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
