You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/10/12 23:49:05 UTC
[jira] [Commented] (CALCITE-918) createProject in RelOptUtil should
uniquify fields
[ https://issues.apache.org/jira/browse/CALCITE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14953804#comment-14953804 ]
Julian Hyde commented on CALCITE-918:
-------------------------------------
Which version of Calcite did you see this? AggregateProjectMergeRule now uses RelBuilder.project, which I believe makes field names unique.
> createProject in RelOptUtil should uniquify fields
> --------------------------------------------------
>
> Key: CALCITE-918
> URL: https://issues.apache.org/jira/browse/CALCITE-918
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.4.0-incubating
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Fix For: 1.5.0-incubating
>
>
> The method
> {code}
> public static RelNode createProject(
> final RelFactories.ProjectFactory factory,
> final RelNode child, final List<Integer> posList)
> {code}
> in RelOptUtil should uniquify fields before creating the Project operator. Otherwise, we might end up hitting an assertion in the Project constructor. This behavior was observed using the AggregateProjectMergeRule rule.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)