[jira] [Commented] (PHOENIX-2505) Unexpected error caused by GROUP BY

["James Taylor (JIRA)" <ji...@apache.org>]

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

James Taylor commented on PHOENIX-2505:
---------------------------------------

Thanks for the bug report, [~jelenaf]. Would it be possible to get a full stack trace for the above exception? Also, if you have the chance to put together a complete unit test, that'd save me some time.

> Unexpected error caused by GROUP BY
> -----------------------------------
>
>                 Key: PHOENIX-2505
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2505
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Jelena
>            Priority: Minor
>             Fix For: 4.7.0
>
>
> If you are selecting more than 2 rows, and you have a Boolean and any number type, depending on the order in which you put them in the GROUP BY clause, you get the following error:
> {noformat}Error during Execute
> org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch. DECIMAL cannot be coerced to BOOLEAN
> {noformat}
> Some examples:
> Order that throws error:
> GROUP BY    NUMBER_TYPE,    BOOLEAN,     ANY_TYPE
> GROUP BY    BOOLEAN,     NUMBER_TYPE,     ANY_TYPE
> GROUP BY    BOOLEAN,     ANY_TYPE,     NUMBER_TYPE
> Order that does not throw the error:
> GROUP BY   NUMBER_TYPE,    ANY_TYPE,      BOOLEAN
> GROUP BY   NON_NUMBER_TYPE,     BOOLEAN,    NUMBER_TYPE  ==> NOTE: there can be any number of NON_NUMBER_TYPE columns before the first one
> GROUP BY   NON_BOOLEAN_TYPE,    NUMBER_TYPE,     BOOLEAN   ==> NOTE: there can be any number of NON_BOOLEAN_TYPE columns before the NUMBER_TYPE
>  
> Note: This is not dependent on the order in which the columns are selected



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)