You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "ramkrishna.s.vasudevan (JIRA)" <ji...@apache.org> on 2015/01/16 10:22:34 UTC
[jira] [Resolved] (PHOENIX-1453) Collect row counts per region in
stats table
[ https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ramkrishna.s.vasudevan resolved PHOENIX-1453.
---------------------------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
4.0.0
Resolving as not pushing to 3.0. Pushed to current master and 4.0.
> Collect row counts per region in stats table
> --------------------------------------------
>
> Key: PHOENIX-1453
> URL: https://issues.apache.org/jira/browse/PHOENIX-1453
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Assignee: ramkrishna.s.vasudevan
> Fix For: 4.0.0, 5.0.0
>
> Attachments: Phoenix-1453.patch, Phoenix-1453_1.patch, Phoenix-1453_10.patch, Phoenix-1453_13.patch, Phoenix-1453_15.patch, Phoenix-1453_17.patch, Phoenix-1453_18.patch, Phoenix-1453_2.patch, Phoenix-1453_20.patch, Phoenix-1453_3.patch, Phoenix-1453_7.patch, Phoenix-1453_8.patch, Phoenix-1453_addendum.patch, Phoenix-1453_addendum_1.patch
>
>
> We currently collect guideposts per equal chunk, but we should also capture row counts. Should we have a parallel array with the guideposts that count rows per guidepost, or is it enough to have a per region count?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)