You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Namit Jain (JIRA)" <ji...@apache.org> on 2012/06/20 23:53:42 UTC
[jira] [Created] (HIVE-3167) bad error message for select distinct
*
Namit Jain created HIVE-3167:
--------------------------------
Summary: bad error message for select distinct *
Key: HIVE-3167
URL: https://issues.apache.org/jira/browse/HIVE-3167
Project: Hive
Issue Type: Bug
Reporter: Namit Jain
hive> select distinct * from src;
FAILED: Error in semantic analysis: Line 0:-1 Invalid function 'TOK_ALLCOLREF'
It is very difficult to understand the above error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HIVE-3167) bad error message for select distinct
*
Posted by "Ashutosh Chauhan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ashutosh Chauhan resolved HIVE-3167.
------------------------------------
Resolution: Duplicate
Dupe of HIVE-3199
> bad error message for select distinct *
> ---------------------------------------
>
> Key: HIVE-3167
> URL: https://issues.apache.org/jira/browse/HIVE-3167
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Attachments: HIVE-3167.1.patch
>
>
> hive> select distinct * from src;
> FAILED: Error in semantic analysis: Line 0:-1 Invalid function 'TOK_ALLCOLREF'
> It is very difficult to understand the above error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HIVE-3167) bad error message for select
distinct *
Posted by "Shengsheng Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13401151#comment-13401151 ]
Shengsheng Huang commented on HIVE-3167:
----------------------------------------
In current implementation "select distinct a,b,c" is silently translate to "select a,b,c group by a,b,c". So "select distinct *" is translate to "select * group by *". But * is not handled correctly when processing the GroupBy expressions. Should add some checking when translating select distinct to group by.
> bad error message for select distinct *
> ---------------------------------------
>
> Key: HIVE-3167
> URL: https://issues.apache.org/jira/browse/HIVE-3167
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Attachments: HIVE-3167.1.patch
>
>
> hive> select distinct * from src;
> FAILED: Error in semantic analysis: Line 0:-1 Invalid function 'TOK_ALLCOLREF'
> It is very difficult to understand the above error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HIVE-3167) bad error message for select distinct
*
Posted by "Shengsheng Huang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HIVE-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shengsheng Huang updated HIVE-3167:
-----------------------------------
Attachment: HIVE-3167.1.patch
A simple patch to notify user that select distinct * is not supported at present.
> bad error message for select distinct *
> ---------------------------------------
>
> Key: HIVE-3167
> URL: https://issues.apache.org/jira/browse/HIVE-3167
> Project: Hive
> Issue Type: Bug
> Reporter: Namit Jain
> Attachments: HIVE-3167.1.patch
>
>
> hive> select distinct * from src;
> FAILED: Error in semantic analysis: Line 0:-1 Invalid function 'TOK_ALLCOLREF'
> It is very difficult to understand the above error
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira