You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Till (JIRA)" <ji...@apache.org> on 2019/04/10 18:04:00 UTC
[jira] [Updated] (ASTERIXDB-2482) Insufficiently helpful error
message in GROUP BY query
[ https://issues.apache.org/jira/browse/ASTERIXDB-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Till updated ASTERIXDB-2482:
----------------------------
Affects Version/s: 0.9.4
> Insufficiently helpful error message in GROUP BY query
> ------------------------------------------------------
>
> Key: ASTERIXDB-2482
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2482
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: *DB - AsterixDB, COMP - Compiler, DOC - Documentation, SQL - Translator SQL++
> Affects Versions: 0.9.4
> Reporter: Michael J. Carey
> Assignee: Dmitry Lychagin
> Priority: Major
>
> use cs122aSchema;
> //Hi Professor Carey, if you uncomment the post.post_id
> //part of the query below the program will give the
> //error "Cannot resolve ambiguous alias reference for
> //undefined identifier post in [#2, $user_id]"
> //[CompilationException]
> SELECT /* post.post_id, */ MAX(post.popularity)
> FROM User user, Post post
> WHERE user.user_id = post.user_id
> AND user.title = "Professor"
> AND user.phone IS MISSING
> GROUP BY user.user_id;
> This is a "bad" error message in terms of user experience - it isn't clear to a normal human why the the variable name "post" could be ambiguous - instead they are thinking "how could I possibly be clearer than "post.user_id"?" I realize this is related to visibility of things after the GROUP BY clause, but an error message that conveys that as the issue would be much more helpful. I suspect that this will happen a lot to new users trying to do analytics with AsterixDB.
> I wonder if there are a few sentences that could go in the docs that could help as well?
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)