hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4459) HbaseObjectWritable code is a byte, we will eventually run out of codes
Date Fri, 23 Sep 2011 13:19:26 GMT

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

Todd Lipcon commented on HBASE-4459:
------------------------------------

We probably have to worry that someone has stored HBaseObjectWritables somewhere persistent,
in which case just making the type a short is not backwards-compatible. Perhaps we should
make it a varint, which I believe will encode the same for any existing data, but would be
multibyte-capable?

> HbaseObjectWritable code is a byte, we will eventually run out of codes
> -----------------------------------------------------------------------
>
>                 Key: HBASE-4459
>                 URL: https://issues.apache.org/jira/browse/HBASE-4459
>             Project: HBase
>          Issue Type: Bug
>          Components: io
>            Reporter: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.94.0
>
>
> There are about 90 classes/codes in HbaseObjectWritable currently and Byte.MAX_VALUE
is 127.  In addition, anyone wanting to add custom classes but not break compatibility might
want to leave a gap before using codes and that's difficult in such limited space.
> Eventually we should get rid of this pattern that makes compatibility difficult (better
client/server protocol handshake) but we should probably at least bump this to a short for
0.94.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message