[
https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ramkrishna.s.vasudevan updated PHOENIX-1856:
--------------------------------------------
Attachment: Phoenix-1856_1.patch
As per the current scope of this JIRA we are not exposing the minkey and maxkey
to the client. The minKey and maxKey are directly taken from the Statistics
Tracker so that we don't need to do any comparison. How ever if we want to
expose it in the client side we should have minKey and maxKey in the
GuidePostsInfo so that while calling GuidePostsInfo#combine() we could always
have the min and max key for the table. So added it as a TODO. IF you feel
that is not needed then can remove all those code in GuidePostsInfo.
> 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
> Attachments: Phoenix-1856_1.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)
