[
https://issues.apache.org/jira/browse/CALCITE-2626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17959800#comment-17959800
]
Ian Bertolacci commented on CALCITE-2626:
-----------------------------------------
> Why do we even need Frames?
Digging into table aliasing, I think I understand why this needs to exist,
which is to maintain the alias names which are not preserved in the RelNodes.
I think this gets back to [this thread we had about making Frame information
available to users of the
RelBuilder.|https://lists.apache.org/[email protected]:gte=0d:bertolacci%20Frame]
I think that would make my problems go away.
> RelBuilder generates wrong field list for join
> ----------------------------------------------
>
> Key: CALCITE-2626
> URL: https://issues.apache.org/jira/browse/CALCITE-2626
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.17.0
> Reporter: Pavel Gubin
> Priority: Major
>
> When building OUTER JOIN RelBuilder doesn't change nullability of underlying
> fields just copying them as is. But with outer join fields shall become
> nullable at appropriate sides of join.
> The error is at these lines:
> https://github.com/apache/calcite/blob/fb7914ec61fc57c8348d9da144e2fbd608c00c61/core/src/main/java/org/apache/calcite/tools/RelBuilder.java#L1546
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
