[ https://issues.apache.org/jira/browse/PHOENIX-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205443#comment-16205443 ]
James Taylor edited comment on PHOENIX-4283 at 10/16/17 5:22 AM: ----------------------------------------------------------------- One last nit: swap the argument order here so that the expected value is first or the assertion message if it were to fail would be confusing. {code} assertEquals(rs.getLong(1),4444444444444444444L); {code} Then make sure your new test passes and commit to 4.12-HBase-0.98, 4.x-HBase-0.98, and master branches. was (Author: jamestaylor): One last nit: swap the argument order here so that the expected value is first or the assertion message if it were to fail would be confusing. Then commit to 4.12-HBase-0.98, 4.x-HBase-0.98, and master branches. > 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 > Assignee: Ethan Wang > Fix For: 4.12.1 > > Attachments: PHOENIX-4283-v2.patch, PHOENIX-4283.patch > > > *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)