[jira] [Comment Edited] (ASTERIXDB-1847) Confusing ambiguous alias error message

["Michael J. Carey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/ASTERIXDB-1847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931422#comment-15931422 ] 

Michael J. Carey edited comment on ASTERIXDB-1847 at 3/18/17 10:30 PM:
-----------------------------------------------------------------------

PPS: Note that this can probably be done as a one-line change.  :-)
(Well maybe two - might be one with the error msg and one where the backquotes would have to be added to be emitted.)


was (Author: dtabass):
PPS: Note that this can probably be done as a one-line change.  :-)
(Well maybe two - might be one with the error msg and one where the backquotes would have to be added to be be emitted.)

> 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)