[
https://issues.apache.org/jira/browse/ASTERIXDB-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931418#comment-15931418
]
Michael J. Carey commented on ASTERIXDB-1847:
---------------------------------------------
Then I think one could make the error message "clearer" by dropping the a-word:
ambiguous. And maybe even the other a-word: alias. We could simply say:
"Cannot resolve the reference for identifier `name` [AlgebricksException]"
I think that's actually clearer - the "ambiguity" is misleading/confusing, I
think, and the "undefined" in the original msg also seems like it goes without
saying. (If it was defined, presumably we wouldn't be having resolution
issues. :-))
I think that this shorter error message would more quickly focus the query
author on the crux of the problem.
> Confusing ambiguous alias error message
> ---------------------------------------
>
> Key: ASTERIXDB-1847
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1847
> Project: Apache AsterixDB
> Issue Type: Bug
> Reporter: Michael J. Carey
> Assignee: Yingyi Bu
> Attachments: HW8_DataInit.txt, HW8_TableInit.txt
>
>
> This query, when run on the attached data:
> USE TopicalBird;
> SELECT btag, about FROM Chirps WHERE about IN
> (SELECT Topics.tid FROM Topics WHERE name = 'Kindle' OR name = 'Surface') ;
> Yields this error msg:
> Cannot resolve ambiguous alias reference for undefined identifier name
> [AlgebricksException]
> It's not obvious to naive users (or me :-)) why this is an ambiguous
> reference. Could we improve this error msg somehow? This may be a fairly
> typical error pattern for SQL --> SQL++ users -- i.e., they are used to SQL's
> unqualified column-naming permissiveness, and will carry those habits into
> NoSQL-land and then be perplexed at times.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
