[
https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519797#comment-14519797
]
ramkrishna.s.vasudevan commented on PHOENIX-1856:
-------------------------------------------------
Why do you think the MAX_KEY will be wrong? What ever guidePosts we get for
that region when it is splitting will any way be forming the minkey for the
left region and the max key for the right region. But the left region's max
key will be the last of the guideposts associated with that region.
you say it is wrong may be because it was not the exact max key ?
> Include min and max row key for each region in stats row
> --------------------------------------------------------
>
> Key: PHOENIX-1856
> URL: https://issues.apache.org/jira/browse/PHOENIX-1856
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Assignee: ramkrishna.s.vasudevan
> Fix For: 5.0.0, 4.4.0
>
> Attachments: Phoenix-1856_1.patch, Phoenix-1856_2.patch
>
>
> It'd be useful to record the min and max row key for each region to make it
> easier to filter guideposts through queries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
