You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2015/10/13 11:30:05 UTC

[jira] [Resolved] (CALCITE-918) createProject in RelOptUtil should uniquify field names

     [ https://issues.apache.org/jira/browse/CALCITE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jesus Camacho Rodriguez resolved CALCITE-918.
---------------------------------------------
    Resolution: Fixed

Thanks [~julianhyde] for reviewing it.

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/13f6efd.

> createProject in RelOptUtil should uniquify field names
> -------------------------------------------------------
>
>                 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)