[
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_addendum_1.patch
Addendum patch that does not increment midEndIndex. Also found an issue in
compaction when the rowCount was incremented even after the result is empty.
Also during splits, we update the rowCount and bytecount via splitStats and at
the same time compaction also updates. So we are not able to get a consistent
result for the rowCount and byteCount. So for now I have not asserted them
when doing a select from the STATS table. How ever on the client side it has
been asserted. All tests passes with this. Will commit this now.
> 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_17.patch, Phoenix-1453_18.patch, Phoenix-1453_2.patch,
> Phoenix-1453_20.patch, Phoenix-1453_3.patch, Phoenix-1453_7.patch,
> Phoenix-1453_8.patch, Phoenix-1453_addendum.patch,
> Phoenix-1453_addendum_1.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)
