phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Sadowski (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-4283) Group By statement truncating BIGINTs
Date Wed, 11 Oct 2017 23:56:01 GMT
Steven Sadowski created PHOENIX-4283:
----------------------------------------

             Summary: Group By statement truncating BIGINTs
                 Key: PHOENIX-4283
                 URL: https://issues.apache.org/jira/browse/PHOENIX-4283
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.11.0
            Reporter: Steven Sadowski


*Versions:*
Phoenix 4.11.0
HBase: 1.3.1
(Amazon EMR: 5.8.0)

*Steps to reproduce:*
1. From the `sqlline-thin.py` client setup the following table:
{code:sql}
CREATE TABLE test_table (
    a BIGINT NOT NULL, 
    c BIGINT NOT NULL
    CONSTRAINT PK PRIMARY KEY (a, c)
);

UPSERT INTO test_table(a,c) VALUES(4444444444444444444, 5555555555555555555);

SELECT a FROM (SELECT a, c FROM test_table GROUP BY a, c) GROUP BY a, c;
{code}


*Expected Result:*
{code:sql}
+----------------------+
|          A           |
+----------------------+
| 4444444444444444444  |
+----------------------+
{code}

*Actual Result:*
{code:sql}
+----------------------+
|          A           |
+----------------------+
| 4444444444444000000  |
+----------------------+
{code}

*Comments:*
Having the two Group By statements together seems to truncate the last 6 or so digits of the
final result. Removing the outer (or either) group by will produce the correct result.

Please fix the Group by statement to not truncate the outer result's value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message