[
https://issues.apache.org/jira/browse/PHOENIX-2769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197025#comment-15197025
]
Ankit Singhal commented on PHOENIX-2769:
----------------------------------------
[~ryvius], is it possible for you to reproduce this with small data set .
this issue is somewhat similar to PHOENIX-2647(which is already fixed in 4.7).
I tried reproducing it like below but not succeeded.
{code}
0: jdbc:phoenix:localhost> CREATE TABLE DESTINATION_METRICS_TABLE (CREATED_DATE
DATE not null, METRIC_ID CHAR(15) not null, METRIC_VALUE bigint CONSTRAINT PK
PRIMARY KEY(CREATED_DATE ROW_TIMESTAMP, METRIC_ID)) SALT_BUCKETS = 8;
No rows affected (1.275 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE VALUES
('2015-09-12 22:02:11', 'test1', 1);
1 row affected (0.104 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test1', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test4', 2);
1 row affected (0.006 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test5', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test6', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test7', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test7', 2);
1 row affected (0.006 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test7', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> UPSERT INTO DESTINATION_METRICS_TABLE(METRIC_ID,
METRIC_VALUE) VALUES ('test7', 2);
1 row affected (0.005 seconds)
0: jdbc:phoenix:localhost> update statistics DESTINATION_METRICS_TABLE;
No rows affected (0.082 seconds)
0: jdbc:phoenix:localhost> select * from system.stats;
+----------------------------+----------------+-----------------+--------------------+--------------------------+------------------------+
| PHYSICAL_NAME | COLUMN_FAMILY | GUIDE_POST_KEY |
GUIDE_POSTS_WIDTH | LAST_STATS_UPDATE_TIME | GUIDE_POSTS_ROW_COUNT |
+----------------------------+----------------+-----------------+--------------------+--------------------------+------------------------+
| DESTINATION_METRICS_TABLE | | | null
| 2016-03-16 08:33:58.167 | null |
| DESTINATION_METRICS_TABLE | 0 | [B@6fa46769 | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@128157c2 | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@69a88b0b | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@3840b55e | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@20434b2c | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@21fc4640 | 113
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@3968252e | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@64610c73 | 65
| | 1 |
| DESTINATION_METRICS_TABLE | 0 | [B@1f788581 | 65
| | 1 |
+----------------------------+----------------+-----------------+--------------------+--------------------------+------------------------+
10 rows selected (0.06 seconds)
0: jdbc:phoenix:localhost> select CREATED_DATE from DESTINATION_METRICS_TABLE
order by created_date desc;
+--------------------------+
| CREATED_DATE |
+--------------------------+
| 2016-03-16 08:33:52.367 |
| 2016-03-16 08:33:51.502 |
| 2016-03-16 08:33:51.478 |
| 2016-03-16 08:33:51.453 |
| 2016-03-16 08:33:51.426 |
| 2016-03-16 08:33:51.399 |
| 2016-03-16 08:33:51.373 |
| 2016-03-16 08:33:51.345 |
| 2015-09-12 22:02:11.000 |
+--------------------------+
9 rows selected (0.122 seconds)
0: jdbc:phoenix:localhost> explain select CREATED_DATE from
DESTINATION_METRICS_TABLE order by created_date desc;
+---------------------------------------------------------------------------------------------------+
| PLAN
|
+---------------------------------------------------------------------------------------------------+
| CLIENT 17-CHUNK 9 ROWS 633 BYTES PARALLEL 8-WAY REVERSE FULL SCAN OVER
DESTINATION_METRICS_TABLE |
| ROW TIMESTAMP FILTER [0, 1458117294005)
|
| SERVER FILTER BY FIRST KEY ONLY
|
| CLIENT MERGE SORT
|
+---------------------------------------------------------------------------------------------------+
4 rows selected (0.015 seconds)
{code}
> Order by desc return wrong results
> ----------------------------------
>
> Key: PHOENIX-2769
> URL: https://issues.apache.org/jira/browse/PHOENIX-2769
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.6.0, 4.7.0
> Environment: 3 centos servers
> Reporter: Joseph Sun
> Labels: test
>
> create table access_logs (
> event_time date not null,
> uuid varchar(36) not null,
> event_type varchar(32),
> CONSTRAINT pk PRIMARY KEY (event_time,uuid)
> ) VERSIONS=1,SALT_BUCKETS=6,IMMUTABLE_ROWS=true;
> I insert 2,000,000 records to access_logs ,and event_time between 2016-01-06
> to 2016-03-15 .
> I execute SQL.
> >select event_time from access_logs order by event_time asc limit 10;
> +--------------------------+
> | EVENT_TIME |
> +--------------------------+
> | 2016-01-06 18:41:54.000 |
> | 2016-01-06 19:56:46.000 |
> | 2016-01-06 20:25:12.000 |
> | 2016-01-06 20:41:37.000 |
> | 2016-01-06 20:46:20.000 |
> | 2016-01-06 20:53:10.000 |
> | 2016-01-06 21:04:09.000 |
> | 2016-01-07 01:22:57.000 |
> | 2016-01-07 10:59:11.000 |
> | 2016-01-07 12:52:56.000 |
> +--------------------------+
>
> > select event_time from access_logs order by event_time desc limit 10;
> +--------------------------+
> | EVENT_TIME |
> +--------------------------+
> | 2016-02-11 13:07:25.000 |
> | 2016-02-11 13:07:24.000 |
> | 2016-02-11 13:07:24.000 |
> | 2016-02-11 13:07:23.000 |
> | 2016-02-11 13:07:23.000 |
> | 2016-02-11 13:07:22.000 |
> | 2016-02-11 13:07:21.000 |
> | 2016-02-11 13:07:21.000 |
> | 2016-02-11 13:07:20.000 |
> | 2016-02-11 13:07:20.000 |
> > select event_time from access_logs where event_time>to_date('2016-02-11
> > 13:07:25') order by event_time desc limit 10;
> +--------------------------+
> | EVENT_TIME |
> +--------------------------+
> | 2016-02-25 18:34:17.000 |
> | 2016-02-25 18:34:17.000 |
> | 2016-02-25 18:34:16.000 |
> | 2016-02-25 18:34:16.000 |
> | 2016-02-25 18:34:15.000 |
> | 2016-02-25 18:34:15.000 |
> | 2016-02-25 18:34:14.000 |
> | 2016-02-25 18:34:14.000 |
> | 2016-02-25 18:34:14.000 |
> | 2016-02-25 18:34:14.000 |
> +--------------------------+
> Check the return results ,the 'order by event_time desc' is not return
> correct results.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
