[
https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519154#comment-14519154
]
ramkrishna.s.vasudevan commented on PHOENIX-1856:
-------------------------------------------------
bq. It turns out, we'll only need MIN_KEY.
Okie, I got the intention. I will still leave the MAX_KEY part. We are just
going to populate it.
I have changed the other minor nits.
bq.(which will become at regular Key Value column instead)
Not getting this. You mean the MIN_KEY should consist the entire key value and
not just the row bytes?
> 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)
