[
https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520836#comment-14520836
]
ramkrishna.s.vasudevan commented on PHOENIX-1856:
-------------------------------------------------
Thanks [~rajeshbabu]. I think the QA took more time to report. And interesting
thing is, similar change was there in the _1 patch itself and the QA did not
complain about it. :)
> Include min 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,
> Phoenix-1856_4.patch, Phoenix-1856_addendum.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)
