You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Jelena (JIRA)" <ji...@apache.org> on 2015/12/10 00:00:16 UTC
[jira] [Updated] (PHOENIX-2505) Unexpected error caused by GROUP BY
[ https://issues.apache.org/jira/browse/PHOENIX-2505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jelena updated PHOENIX-2505:
----------------------------
Description:
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
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /. Reason:
<pre> org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch. DECIMAL cannot be coerced to BOOLEAN</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>{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
was:
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
S1000(2020)[Simba][Phoenix] (2020) An error occured while trying to fetch a result set: <html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 500 </title>
</head>
<body>
<h2>HTTP ERROR: 500</h2>
<p>Problem accessing /. Reason:
<pre> org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch. DECIMAL cannot be coerced to BOOLEAN</pre></p>
<hr /><i><small>Powered by Jetty://</small></i>
</body>
</html>{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
> 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
>
> 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
> <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
> <title>Error 500 </title>
> </head>
> <body>
> <h2>HTTP ERROR: 500</h2>
> <p>Problem accessing /. Reason:
> <pre> org.apache.phoenix.schema.TypeMismatchException: ERROR 203 (22005): Type mismatch. DECIMAL cannot be coerced to BOOLEAN</pre></p>
> <hr /><i><small>Powered by Jetty://</small></i>
> </body>
> </html>{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
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)