[
https://issues.apache.org/jira/browse/PHOENIX-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gabriel Reid resolved PHOENIX-264.
----------------------------------
Resolution: Fixed
Bulk resolve of closed issues imported from GitHub. This status was reached by
first re-opening all closed imported issues and then resolving them in bulk.
> Parallelize non aggregate queries
> ---------------------------------
>
> Key: PHOENIX-264
> URL: https://issues.apache.org/jira/browse/PHOENIX-264
> Project: Phoenix
> Issue Type: Task
> Reporter: Raymond Liu
>
> I have following two queries with exactly the same condition while one of it
> use count another not.:
> SELECT count(F0.C0), count(F0.C1), count(F0.C2) FROM "200M18C96R_M" WHERE
> (F0.C1 > 518 AND F0.C1 < 520) AND (F0.C7 > 9800); ------
> COUNT(C0) COUNT(C1) COUNT(C2)
> --------- --------- ---------
> 192 192 192
> Time: 123.523 sec(s)
> SELECT F0.C0, F0.C1, F0.C2 FROM "200M18C96R_M" WHERE (F0.C1 > 518 AND F0.C1 <
> 520) AND (F0.C7 > 9800);
> C0 C1 C2
> --- ---- --------
> j 519 4918304619306952458
> a 519 2364958063320048744
> s 519 4918304619306952458
> a 519 2364958063320048744
> d 519 4918304619306952458
> o 519 2364958063320048744
> d 519 4918304619306952458
> .
> .
> .
> Time: 2057.106 sec(s)
> The table is around 200M lines. scan cache set to 1000, only 192 row will
> match, thus no much data to transfer to client. So as I understand, it should
> roughly finish in similar time.
> while the actual time difference is 15x, seems in the second case, the RS is
> not fully working, often idle from time to time during the process.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
