[
https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266501#comment-14266501
]
James Taylor commented on PHOENIX-1453:
---------------------------------------
One more comment: given that rowCount and byteCount are stored as a single
number on GuidePostInfo, I don't think there's a need for a separate
GuidePostRegionInfo class. The two will do exactly the same thing: combine()
sums the rowCount and byteCount and combines the guidepost row keys; and we'll
have incremental methods for adding a single guidepost, adding a byteCount, and
incrementing the rowCount. If this is correct, I think we should just stick
with one class: GuidePostInfo.
> 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_13.patch, Phoenix-1453_15.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)
