[
https://issues.apache.org/jira/browse/CALCITE-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954691#comment-14954691
]
Jesus Camacho Rodriguez commented on CALCITE-918:
-------------------------------------------------
[~julianhyde], it was based on 1.4, the version currently used by Hive.
Once we upgrade to 1.5, we won't even call that createProject method. However I
will commit this fix, as I think it makes sense to uniquify those field names.
> 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)
