phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-1453) Collect row counts per region in stats table
Date Fri, 26 Dec 2014 07:47:13 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

ramkrishna.s.vasudevan updated PHOENIX-1453:
--------------------------------------------
    Attachment: Phoenix-1453_10.patch
                Phoenix-1453_10.patch

Attaching a patch that tries to create GuidePostsInfo and GuidePostsRegionInfo.  The approximation
on the rowcount and bytecount is not done as suggested in the previous count.  That would
be a simpler change anyway as it has to be applied on the GuidePostsInfo only.
May be should we introduce a new field in the .proto file called GuidePostsInfo and repopulate
the cf, list of guideposts followed by rowCount and bytecount arrays. 

> 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
>         Attachments: Phoenix-1453.patch, Phoenix-1453_1.patch, Phoenix-1453_10.patch,
Phoenix-1453_2.patch, Phoenix-1453_3.patch, Phoenix-1453_7.patch, Phoenix-1453_8.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)

Mime
View raw message