[
https://issues.apache.org/jira/browse/PHOENIX-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276486#comment-14276486
]
James Taylor commented on PHOENIX-1453:
---------------------------------------
midEndIndex will never be -1. See this code:
{code}
+ if (index < 0) {
+ midEndIndex = midStartIndex = -(index + 1);
+ } else {
+ // For an exact match, we want to get rid of the exact
match guidepost,
+ // since it's replaced by the region boundary.
+ midEndIndex = index;
+ midStartIndex = index + 1;
+ }
{code}
> 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
>
>
> 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)
