[
https://issues.apache.org/jira/browse/CALCITE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636892#comment-17636892
]
Julian Hyde commented on CALCITE-5391:
--------------------------------------
With any rule, there's a possibility that the resulting relational expression
matches an existing relational expression that has different field names.
> JoinOnUniqueToSemiJoinRule should preserve field names
> ------------------------------------------------------
>
> Key: CALCITE-5391
> URL: https://issues.apache.org/jira/browse/CALCITE-5391
> Project: Calcite
> Issue Type: Bug
> Affects Versions: 1.32.0
> Reporter: Scott Reynolds
> Assignee: Scott Reynolds
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.33.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The new rule pushes a copy of the [original project without the alias
> names|https://github.com/apache/calcite/pull/2848/files#r1026959819]
> {code:java}
> builder.project(project.getProjects());
> {code}
> This results in a new SQL plan without the name fields -- they become {{$fN}}
> fields in different plans.
> Small change is required to put the names from the {{RelDataType}} of the
> {{Project}} similar to the other {{Semijoin}} rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
