You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/24 04:25:39 UTC
[jira] [Resolved] (PHOENIX-1515) explain time is too long
[ https://issues.apache.org/jira/browse/PHOENIX-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor resolved PHOENIX-1515.
-----------------------------------
Resolution: Fixed
Assignee: James Taylor
Fix Version/s: 4.6.0
Fixed a while back by ensuring execution not started when doing an explain.
> explain time is too long
> ------------------------
>
> Key: PHOENIX-1515
> URL: https://issues.apache.org/jira/browse/PHOENIX-1515
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.2.0
> Reporter: yang ming
> Assignee: James Taylor
> Fix For: 4.6.0
>
>
> There are two Phoenix tables:YK.VIDEO_SUMMARY_NEW,YK.VIDEO_REGION,primary key contains videoid.
> Each table has about 60,000 million rows,before query likes the following cost in millisecond,but now quering table YK.VIDEO_REGION cost nearly 10s,table YK.VIDEO_SUMMARY_NEW still in millisecond.
> Also the explains have the same results,so what cause this problem?
> 0: jdbc:phoenix:10.103.23.82> select * from YK.VIDEO_SUMMARY_NEW where videoid=183705534 and date=to_date('20141203','yyyyMMdd') limit 2;
> +------------+---------------------+------------+------------+-------------+------------+------------+------------+------------+------------+------------+------------+--------+
> | VIDEOID | DATE | PLATFORM | DEVICE | SYSTEMGROUP | SYSTEM | VV | TS | UP | DOWN | COMMENT | FAVORI | FAVO |
> +------------+---------------------+------------+------------+-------------+------------+------------+------------+------------+------------+------------+------------+--------+
> | 183705534 | 2014-12-03 | app | computer | windows | windows | 870 | 663450 | null | null | null | null | null |
> | 183705534 | 2014-12-03 | app | mobile | android | android | 21639 | 9232508 | null | null | null | null | null |
> +------------+---------------------+------------+------------+-------------+------------+------------+------------+------------+------------+------------+------------+--------+
> {color:red}
> 2 rows selected (0.325 seconds)
> {color}
> 0: jdbc:phoenix:10.103.23.82> select * from YK.VIDEO_REGION where videoid=183705534 and date=to_date('20141203','yyyyMMdd') limit 2;
> +------------+---------------------+------------+------------+------------+------------+------------+------------+
> | VIDEOID | DATE | PLATFORM | DEVICE | PROVINCEID | CITYID | VV | TS |
> +------------+---------------------+------------+------------+------------+------------+------------+------------+
> | 183705534 | 2014-12-03 | app | computer | 11 | 110000 | 39 | 30925 |
> | 183705534 | 2014-12-03 | app | computer | 12 | 120000 | 20 | 6021 |
> +------------+---------------------+------------+------------+------------+------------+------------+------------+
> {color:red}
> 2 rows selected (8.169 seconds)
> {color}
> 0: jdbc:phoenix:10.103.23.82> explain select * from YK.VIDEO_SUMMARY_NEW where videoid=183705534 and date=to_date('20141203','yyyyMMdd') limit 2;
> +------------+
> | PLAN |
> +------------+
> | CLIENT PARALLEL 30-WAY RANGE SCAN OVER YK.VIDEO_SUMMARY_NEW [0,183705534,'2014-12-03 00:00:00.000'] |
> | SERVER FILTER BY PageFilter 2 |
> | SERVER 2 ROW LIMIT |
> | CLIENT MERGE SORT |
> | CLIENT 2 ROW LIMIT |
> +------------+
> {color:red}
> 5 rows selected (0.056 seconds)
> {color}
> 0: jdbc:phoenix:10.103.23.82> explain select * from YK.VIDEO_REGION where videoid=183705534 and date=to_date('20141203','yyyyMMdd') limit 2;
> +------------+
> | PLAN |
> +------------+
> | CLIENT PARALLEL 30-WAY RANGE SCAN OVER YK.VIDEO_REGION [0,183705534,'2014-12-03 00:00:00.000'] |
> | SERVER FILTER BY PageFilter 2 |
> | SERVER 2 ROW LIMIT |
> | CLIENT MERGE SORT |
> | CLIENT 2 ROW LIMIT |
> +------------+
> {color:red}
> 5 rows selected (8.109 seconds)
> {color}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)