hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ryan rawson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2219) stop using code mapping for method names in the RPC
Date Mon, 15 Feb 2010 19:41:28 GMT

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

ryan rawson commented on HBASE-2219:
------------------------------------

I am going to commit this to trunk ASAP so it gets into 0.21 sooner than later.

Now, the question is, do we expect to maintain the 0.20.x branch longer, and if so are we
willing to take a 1 time hit to get more expandability. I'm thinking "no".

> stop using code mapping for method names in the RPC
> ---------------------------------------------------
>
>                 Key: HBASE-2219
>                 URL: https://issues.apache.org/jira/browse/HBASE-2219
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: ipc
>    Affects Versions: 0.20.3
>            Reporter: ryan rawson
>            Priority: Blocker
>             Fix For: 0.21.0
>
>         Attachments: HBASE-2219-2.patch, HBASE-2219.patch
>
>
> since we use a sorted mapping of method names -> codes and send that over the wire,
even trivial changes, such as adding a new call, become wire-incompatible.  This means many
features which could easily have gone into a minor update must wait for a major update.  Eg:
2066, 1845, etc.
> This will increase on-wire overhead, but the compatibility is worth it I think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message