[
https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237609#comment-14237609
]
James Taylor commented on PHOENIX-1453:
---------------------------------------
Also, thinking about this more, I do think it'd be better to just keep a per
region per cf row count (like we do with bytes). That way we don't need a
BIGINT ARRAY, but can have a single BIGINT value. In GuidePostInfo, though,
it'd be useful to expand this to be parallel to the guideposts array. Either
that, or provide a bit more structure around the GuidepostInfo: for example,
more of a structure with key[], row count, and byte count which repeats.
> 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, Phoenix-1453_7.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)
