[
https://issues.apache.org/jira/browse/CALCITE-4025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17117157#comment-17117157
]
Julian Hyde commented on CALCITE-4025:
--------------------------------------
I'd like to see a test case. Looking up qualified names is complicated, because
if you have "FROM x.y.z" as a table then later you are allowed to use the
fully-qualified table name as if it were a table alias, e.g. "SELECT x.y.z.c"
and "SELECT z.c" are both valid.
> 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
> Priority: Major
>
> 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)
