[
https://issues.apache.org/jira/browse/CALCITE-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181450#comment-17181450
]
Laurent Goujon commented on CALCITE-4025:
-----------------------------------------
Thinking more about it (and before changing the issue's title), I wonder if
there's not a second issue at hand which is the case where both the alias and
the column have the exact same case, and it would be ambiguous to resolve but
currently it does not fail?
> DelegatingScope#fullyQualify may exit too soon when resolving table alias
> -------------------------------------------------------------------------
>
> Key: CALCITE-4025
> URL: https://issues.apache.org/jira/browse/CALCITE-4025
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Laurent Goujon
> Assignee: Laurent Goujon
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> When fully qualifing an id with {{DelegatingScope#fullyQualify()}} method,
> there's a look going over all the possible sub prefixes and trying to resolve
> them, until one succeed. But if not, the same lookup is done using a liberal
> name matcher. If that one resolves, then the method exit early with an
> exception message instead of going over the whole loop or trying for a fully
> qualified table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
