[
https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519808#comment-14519808
]
James Taylor commented on PHOENIX-1856:
---------------------------------------
Main point is we don't need it. Secondary point is, yes it won't be the correct
MAX_KEY - there will be keys bigger than the last of the guideposts. So since
we don't need it and it would be somewhat misleading information, I think it'd
be good not to collect it.
> 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)
