[
https://issues.apache.org/jira/browse/CALCITE-5391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17637977#comment-17637977
]
Scott Reynolds commented on CALCITE-5391:
-----------------------------------------
Thanks so much, after reading that through and looking at a bunch of calcite
code I understand now. In my application, we will have to adopt much the same
way as the JDBC implementation within Calcite adopts. And had we done that, our
application wouldn't have broke. Thanks for sharing CALCITE-1584.
I have updated the pull request with tests and links to this issue.
> JoinOnUniqueToSemiJoinRule should preserve field names, if possible
> -------------------------------------------------------------------
>
> 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)
