[
https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14225818#comment-14225818
]
ramkrishna.s.vasudevan commented on PHOENIX-1453:
-------------------------------------------------
bq.It's fine if you update the SYSTEM.STATS table with the ROW_COUNT information
James, the BC am saying here is not with the ROW_COUNT column that we add and
the way that column is populated. What am saying is about the ROW_COUNT info
added along with the value of the Cell. That would help to recreate a
GuidePostInfo directly by reading the GUIDE_POSTS_BYTES column.
If that is not needed then while reading the stats we should add this column
ROW_COUNT also and then retrieve that cell's value and then create the
guideposts info.
That would ofcourse not need any BC related changes.
> 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
>
>
> 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)
