hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4616) Update hregion encoded name to reduce logic and prevent region collisions in META
Date Thu, 22 Dec 2011 22:21:30 GMT

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

stack commented on HBASE-4616:
------------------------------

You can't remove them w/o deprecating them first.

On your other comments:

What about my proposal that you narrow scope of this patch and attach the priority issue,
removing get closestorbefore, and do uuid/md5'ing in another issue?

'!' is not legal table char.  Here is the function that tests legal characters: http://hbase.apache.org/xref/org/apache/hadoop/hbase/HTableDescriptor.html#278
 Anything less than '-', the lowest allowable table character should do.  ',' qualifies (just
about) though it would have to be the character to designate the last region and we'd need
another delimiter for non-end-regions... most chars are problematic but could use a '+' (I
think) or a '#' -- but this'd be too ugly... need to think of something better.

Agree on not doing int for table name; problematic when replicating not to mind the complexity
it adds (as you outline above).

I like your pros and cons table.


                
> Update hregion encoded name to reduce logic and prevent region collisions in META
> ---------------------------------------------------------------------------------
>
>                 Key: HBASE-4616
>                 URL: https://issues.apache.org/jira/browse/HBASE-4616
>             Project: HBase
>          Issue Type: Umbrella
>            Reporter: Alex Newman
>            Assignee: Alex Newman
>         Attachments: HBASE-4616-v2.patch, HBASE-4616-v3.patch, HBASE-4616.patch
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message