You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Sean Hsuan-Yi Chu (JIRA)" <ji...@apache.org> on 2015/10/01 00:54:04 UTC
[jira] [Commented] (CALCITE-900) ProjectSetOpTransposeRule can be
improved when the input is a SetOperator with Trivial Project on top
[ https://issues.apache.org/jira/browse/CALCITE-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939012#comment-14939012 ]
Sean Hsuan-Yi Chu commented on CALCITE-900:
-------------------------------------------
The problem is we have observed volcano planning going on forever.
Initially, we thought that trivial project might be a problem. So we tried something around that trivial project.
But I found out that it does not really resolve the problem.
Now I am trying to reproduce the problem in Calcite, without going to Drill. That might narrow down things.
> ProjectSetOpTransposeRule can be improved when the input is a SetOperator with Trivial Project on top
> -----------------------------------------------------------------------------------------------------
>
> Key: CALCITE-900
> URL: https://issues.apache.org/jira/browse/CALCITE-900
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Sean Hsuan-Yi Chu
> Assignee: Julian Hyde
> Attachments: trace.log
>
>
> When SetOperator with Trivial Project on top, pushing this trivial project does not necessary. An improvement can be done if we just discard this trivial project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)