[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-13 Thread Pham Phuong Tu (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060082#comment-14060082
 ] 

Pham Phuong Tu commented on PHOENIX-1057:
-

You may know that Hbase 0.98.0 and 0.98.1+ don't have any isssue related with 
this bug, of couse, i think this bug still appear in 0.98.1+, my sample very 
short and clear, every body can reproceduce this bug. Thanks.

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time ORDER BY hour_time
 +++
 |

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-13 Thread James Taylor (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060085#comment-14060085
 ] 

James Taylor commented on PHOENIX-1057:
---

Actually, I don't know that 0.98.0 doesn't have anything to do with it. If you 
could confirm that the issue occurs on 0.98.1, that would be much appreciated. 
If you're planning on using Phoenix, you'll need to upgrade to 0.98.1 anyway, 
so it's no additional work on your end.

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-07 Thread James Taylor (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14053789#comment-14053789
 ] 

James Taylor commented on PHOENIX-1057:
---

[~phamptu] - if you can repro this on 0.98.1+, please let us know. Otherwise 
I'll go ahead and close this as we don't support any version before 0.98.1.

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  |

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-04 Thread James Taylor (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052259#comment-14052259
 ] 

James Taylor commented on PHOENIX-1057:
---

What version of Phoenix and HBase are you using? If you can provide a complete 
unit test that reproduces the issue, we'll be happy to fix it.

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
 E.g: 
  SELECT count(1) AS total, hour_time FROM device2 where hour_time 
  =1403974800 and hour_time  1404061199 GROUP BY hour_time ORDER BY 
  hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 90 | 1403974800 |
 | 73 | 1403978400 |
 | 70 | 1403982000 |
 | 66 | 1403985600 |
 | 51 | 1403989200 |
 | 39 | 1403992800 |
 | 33 | 1403996400 |
 | 73 | 1404003600 |
 | 77 | 1404007200 |
 | 77 | 1404010800 |
 | 97 | 1404014400 |
 | 74 | 1404018000 |
 | 92 | 1404021600 |
 | 84 | 1404025200 |
 | 83 | 1404028800 |
 | 89 | 1404032400 |
 | 93 | 1404036000 |
 | 93 | 1404039600 |
 | 99 | 1404043200 |
 | 120| 1404046800 |
 | 113| 1404050400 |
 | 85 | 1404054000 |
 | 80 | 1404057600 |
 +++
 The result of this query return missing value 140400 of hour_time, of 
 course 1403974800 = 140400  1404061199.
 After run 2 queries below, we can see that value 140400 exist in device2 
 table:
  select distinct hour_time from device2 where day_time = 1403974800 order 
  by hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
  SELECT count(1) AS total, hour_time FROM device2 where day_time 
  =1403974800 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 90 | 1403974800 |
 | 73 | 1403978400 |
 | 70 | 1403982000 |
 | 66 | 1403985600 |
 | 51 | 1403989200 |
 | 39 | 1403992800 |
 | 33 | 1403996400 |
 | 60 | 140400 |
 | 73 | 1404003600 |
 | 77 | 1404007200 |
 | 77 | 1404010800 |
 | 97 | 1404014400 |
 | 74 | 1404018000 |
 | 92 | 1404021600 |
 | 84 | 1404025200 |
 | 83 | 1404028800 |
 | 89 | 1404032400 |
 | 93 | 1404036000 |
 | 93 | 1404039600 |
 | 99 | 1404043200 |
 | 120| 1404046800 |
 | 113| 1404050400 |
 | 85 | 1404054000 |
 | 80 | 1404057600 |
 +++
 This kind of bug resolved in a lot of topic, i don't understand why it still 
 apper:
 http://mail-archives.apache.org/mod_mbox/phoenix-dev/201403.mbox/%3CJIRA.12700068.1394495218035.81228.1394954374732@arcas%3E
 https://groups.google.com/forum/#!topic/phoenix-hbase-user/mZxSFxpqjS4
 http://mail-archives.apache.org/mod_mbox/phoenix-user/201404.mbox/%3c1398727966.67421.yahoomail...@web165003.mail.bf1.yahoo.com%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-04 Thread Pham Phuong Tu (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052296#comment-14052296
 ] 

Pham Phuong Tu commented on PHOENIX-1057:
-

My system eviroment:
- Hadoop 2.4
- Hbase 0.98
- Phoenix 4.0

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
 E.g: 
  SELECT count(1) AS total, hour_time FROM device2 where hour_time 
  =1403974800 and hour_time  1404061199 GROUP BY hour_time ORDER BY 
  hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 90 | 1403974800 |
 | 73 | 1403978400 |
 | 70 | 1403982000 |
 | 66 | 1403985600 |
 | 51 | 1403989200 |
 | 39 | 1403992800 |
 | 33 | 1403996400 |
 | 73 | 1404003600 |
 | 77 | 1404007200 |
 | 77 | 1404010800 |
 | 97 | 1404014400 |
 | 74 | 1404018000 |
 | 92 | 1404021600 |
 | 84 | 1404025200 |
 | 83 | 1404028800 |
 | 89 | 1404032400 |
 | 93 | 1404036000 |
 | 93 | 1404039600 |
 | 99 | 1404043200 |
 | 120| 1404046800 |
 | 113| 1404050400 |
 | 85 | 1404054000 |
 | 80 | 1404057600 |
 +++
 The result of this query return missing value 140400 of hour_time, of 
 course 1403974800 = 140400  1404061199.
 After run 2 queries below, we can see that value 140400 exist in device2 
 table:
  select distinct hour_time from device2 where day_time = 1403974800 order 
  by hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
  SELECT count(1) AS total, hour_time FROM device2 where day_time 
  =1403974800 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 90 | 1403974800 |
 | 73 | 1403978400 |
 | 70 | 1403982000 |
 | 66 | 1403985600 |
 | 51 | 1403989200 |
 | 39 | 1403992800 |
 | 33 | 1403996400 |
 | 60 | 140400 |
 | 73 | 1404003600 |
 | 77 | 1404007200 |
 | 77 | 1404010800 |
 | 97 | 1404014400 |
 | 74 | 1404018000 |
 | 92 | 1404021600 |
 | 84 | 1404025200 |
 | 83 | 1404028800 |
 | 89 | 1404032400 |
 | 93 | 1404036000 |
 | 93 | 1404039600 |
 | 99 | 1404043200 |
 | 120| 1404046800 |
 | 113| 1404050400 |
 | 85 | 1404054000 |
 | 80 | 1404057600 |
 +++
 This kind of bug resolved in a lot of topic, i don't understand why it still 
 apper:
 http://mail-archives.apache.org/mod_mbox/phoenix-dev/201403.mbox/%3CJIRA.12700068.1394495218035.81228.1394954374732@arcas%3E
 https://groups.google.com/forum/#!topic/phoenix-hbase-user/mZxSFxpqjS4
 http://mail-archives.apache.org/mod_mbox/phoenix-user/201404.mbox/%3c1398727966.67421.yahoomail...@web165003.mail.bf1.yahoo.com%3E



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-04 Thread Pham Phuong Tu (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052308#comment-14052308
 ] 

Pham Phuong Tu commented on PHOENIX-1057:
-

Updated bug description, hope that help!

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-04 Thread Jeffrey Zhong (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052707#comment-14052707
 ] 

Jeffrey Zhong commented on PHOENIX-1057:


Just to confirm that you're using hbase0.98.0 or hbase0.98.1+?

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  |

[jira] [Commented] (PHOENIX-1057) Phoenix wrong range query result

2014-07-04 Thread Pham Phuong Tu (JIRA) 

[ 
https://issues.apache.org/jira/browse/PHOENIX-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14052757#comment-14052757
 ] 

Pham Phuong Tu commented on PHOENIX-1057:
-

Confirm that my hbase is 0.98

 Phoenix wrong range query result
 

 Key: PHOENIX-1057
 URL: https://issues.apache.org/jira/browse/PHOENIX-1057
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.0.0
 Environment: Centos 6.5, Hbase 0.98
Reporter: Pham Phuong Tu
  Labels: bug, query

 Hi guys,
 I have one big problem with Phoenix is some time, range query like: , , =, 
 = return missing one or more result, 
  REPROCEDURE ERROR CASE: 
 CREATE TABLE IF NOT EXISTS device3 (id CHAR(50) NOT NULL PRIMARY KEY, 
 manufacture CHAR(50), brand CHAR(50), model CHAR(50), os CHAR(50), os_version 
 CHAR(50), resolution CHAR(50), language CHAR(50), carrier CHAR(50), country 
 CHAR(50), day_time INTEGER, time INTEGER, hour_time INTEGER, status INTEGER);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('1',1403974800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('2',1403978400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('3',1403982000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('4',1403985600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('5',1403989200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('6',1403992800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('7',1403996400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('8',140400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('9',1404003600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('10',1404007200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('11',1404010800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('12',1404014400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('13',1404018000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('14',1404021600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('15',1404025200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('16',1404028800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('17',1404032400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('18',1404036000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('19',1404039600,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('20',1404043200,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('21',1404046800,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('22',1404050400,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('23',1404054000,1403974800);
 UPSERT INTO device3(id, hour_time, day_time) values 
 ('24',1404057600,1403974800);
 SELECT count(1) AS total, hour_time FROM device3 where hour_time =1403974800 
 and hour_time  1404061199 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  | 1403989200 |
 | 1  | 1403992800 |
 | 1  | 1403996400 |
 | 1  | 140400 |
 | 1  | 1404003600 |
 | 1  | 1404007200 |
 | 1  | 1404010800 |
 | 1  | 1404014400 |
 | 1  | 1404018000 |
 | 1  | 1404021600 |
 | 1  | 1404025200 |
 | 1  | 1404028800 |
 | 1  | 1404032400 |
 | 1  | 1404036000 |
 | 1  | 1404039600 |
 | 1  | 1404043200 |
 | 1  | 1404046800 |
 | 1  | 1404050400 |
 | 1  | 1404054000 |
 | 1  | 1404057600 |
 +++
 select distinct hour_time from device3 where day_time = 1403974800 order by 
 hour_time;
 ++
 | HOUR_TIME  |
 ++
 | 1403974800 |
 | 1403978400 |
 | 1403982000 |
 | 1403985600 |
 | 1403989200 |
 | 1403992800 |
 | 1403996400 |
 | 140400 |
 | 1404003600 |
 | 1404007200 |
 | 1404010800 |
 | 1404014400 |
 | 1404018000 |
 | 1404021600 |
 | 1404025200 |
 | 1404028800 |
 | 1404032400 |
 | 1404036000 |
 | 1404039600 |
 | 1404043200 |
 | 1404046800 |
 | 1404050400 |
 | 1404054000 |
 | 1404057600 |
 ++
 SELECT count(1) AS total, hour_time FROM device3 where day_time =1403974800 
 GROUP BY hour_time ORDER BY hour_time
 +++
 |   TOTAL| HOUR_TIME  |
 +++
 | 1  | 1403974800 |
 | 1  | 1403978400 |
 | 1  | 1403982000 |
 | 1  | 1403985600 |
 | 1  |