[ https://issues.apache.org/jira/browse/PHOENIX-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16204219#comment-16204219 ]
James Taylor commented on PHOENIX-4283: --------------------------------------- [~aertoria] - would you have some cycles to take a look? I've confirmed it's an issue in 4.12 using the regular thick driver too. It works fine without the nested query: {code} 0: jdbc:phoenix:localhost:2181:/hbase> UPSERT INTO test_table(a,c) VALUES(4444444444444444444, 5555555555555555555); 1 row affected (0.033 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> SELECT a FROM (SELECT a, c FROM test_table GROUP BY a, c) GROUP BY a, c; +----------------------+ | A | +----------------------+ | 4444444444444000000 | +----------------------+ 1 row selected (0.039 seconds) 0: jdbc:phoenix:localhost:2181:/hbase> SELECT a, c FROM test_table GROUP BY a, c; +----------------------+----------------------+ | A | C | +----------------------+----------------------+ | 4444444444444444444 | 5555555555555555555 | +----------------------+----------------------+ 1 row selected (0.04 seconds) {code} Is that a possible work around for you, [~ssadowski] while we investigate this? > 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 > Fix For: 4.12.1 > > > *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)