Siddharth Wagle created AMBARI-11317:
----------------------------------------

             Summary: Avoid Client side merge sort on aggregator queries
                 Key: AMBARI-11317
                 URL: https://issues.apache.org/jira/browse/AMBARI-11317
             Project: Ambari
          Issue Type: Task
          Components: ambari-metrics
    Affects Versions: 2.0.0
            Reporter: Siddharth Wagle
            Assignee: Siddharth Wagle
             Fix For: 2.1.0


- Existing query plan:
{code}
0: jdbc:phoenix:localhost:61181:/hbase> explain select * from METRIC_RECORD 
WHERE SERVER_TIME > 1432139517000 AND SERVER_TIME < 1432149517000 ORDER BY 
METRIC_NAME, HOSTNAME, APP_ID, SERVER_TIME limit 5760;
+------------+
|    PLAN    |
+------------+
| CLIENT PARALLEL 2-WAY FULL SCAN OVER METRIC_RECORD |
|     SERVER FILTER BY (SERVER_TIME > 1432139517000 AND SERVER_TIME < 
1432149517000) |
|     SERVER TOP 5760 ROWS SORTED BY [METRIC_NAME, HOSTNAME, APP_ID, 
SERVER_TIME] |
| CLIENT MERGE SORT |
+------------+
4 rows selected (0.061 seconds)
{code}

- Modified query plan.
{code}
0: jdbc:phoenix:localhost:61181:/hbase> explain select * from METRIC_RECORD 
WHERE SERVER_TIME > 1432139517000 AND SERVER_TIME < 1432149517000 ORDER BY 
METRIC_NAME, HOSTNAME, SERVER_TIME, APP_ID, INSTANCE_ID limit 5760;
+------------+
|    PLAN    |
+------------+
| CLIENT PARALLEL 1-WAY FULL SCAN OVER METRIC_RECORD |
|     SERVER FILTER BY (SERVER_TIME > 1432139517000 AND SERVER_TIME < 
1432149517000) |
|     SERVER 5760 ROW LIMIT |
| CLIENT 5760 ROW LIMIT |
+------------+
4 rows selected (0.034 seconds)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to