phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1856) Include min and max row key for each region in stats row
Date Wed, 29 Apr 2015 15:55:06 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519608#comment-14519608
] 

James Taylor commented on PHOENIX-1856:
---------------------------------------

Please remove the tracking and setting of MAX_KEY as we don't need it and
it will be incorrect after a split.

As far as the next change I have in mind: The region name is the last
column in our PK constraint. Instead, MIN_KEY would be a better choice.
That's the next change I'd like to make: remove REGION_NAME from the PK and
add MIN_KEY. We'll need to drop and recreate the stats table to do this,
but that's ok b/c it's transient data anyway.


> 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)

Mime
View raw message