[
https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235014#comment-14235014
]
ramkrishna.s.vasudevan commented on PHOENIX-1453:
-------------------------------------------------
[~giacomotaylor]
To track the rowCount also we could add another pojo GuidePostsState - fine but
already we have GuidePostsInfo also. Hence was bit skeptical but I think that
is better so that the tracking would be easier.
Regarding the toBytes() - do you still want the rowCount to be persisted in the
GUIDE_POSTS_BYTE column. Doing that would in anyway want us to deal with cells
without the GUIDE_POSTS_ROW_COUNT and cells with them.
So only by reading the GUIDE_POSTS_ROW_COUNT we could handle it but only thing
is we need to read two cells and also that after reading the cell we need to
combine (or add it with GuidePostsInfo) created from fromBytes().
Also GUIDE_POSTS_ROW_COUNT will any way be serialized as an array.
> 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_2.patch, Phoenix-1453_3.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)
