phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaclav Loffelmann (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1237) COALESCE Function - type of second parameter
Date Wed, 17 Sep 2014 18:00:35 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vaclav Loffelmann updated PHOENIX-1237:
---------------------------------------
    Attachment: PHOENIX-1237.fix2.patch

I've did some changes, but I'm not sure if is it right by your design. I've append some tests
too.
Thanks

> COALESCE Function - type of second parameter
> --------------------------------------------
>
>                 Key: PHOENIX-1237
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1237
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 3.1, 4.1
>            Reporter: Vaclav Loffelmann
>            Assignee: Vaclav Loffelmann
>         Attachments: PHOENIX-1237.fix.patch, PHOENIX-1237.fix2.patch, PHOENIX_1237.patch
>
>
> There is an issue with automatic set data type of second parameter to coalesce function.
> For instance table:
> {code:sql}
> CREATE TABLE IF NOT EXISTS TEST_COALESCE(
> ID BIGINT NOT NULL,
> COUNT UNSIGNED_INT
> CONSTRAINT pk PRIMARY KEY(ID));
> {code}
> and query:
> {code:sql}
> SELECT COALESCE(SUM(COUNT), 0) FROM TEST_SUM GROUP BY ID;
> {code}
> This will cause in:
> {quote}SQLException: ERROR 507 (42846): Cannot convert type. COALESCE expected UNSIGNED_INT,
but got INTEGER {quote}
> Hence second parameter is typed to its input value (eg. 0 is signed int not long), and
long is expected. That is cause for ArrayIndexOutOfBoundsException described in PHOENIX-1229.



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

Mime
View raw message