You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ryan rawson (JIRA)" <ji...@apache.org> on 2010/03/11 20:08:27 UTC
[jira] Commented: (HBASE-2219) stop using code mapping for method
names in the RPC
[ https://issues.apache.org/jira/browse/HBASE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12844171#action_12844171 ]
ryan rawson commented on HBASE-2219:
------------------------------------
I have a pending forward ported patch. Ill commit it soon.
On Mar 11, 2010 1:58 PM, "Jean-Daniel Cryans (JIRA)" <ji...@apache.org>
wrote:
[
https://issues.apache.org/jira/browse/HBASE-2219?page=com.atlassian.jira.plugin.system.issue.
..
> 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
> Assignee: ryan rawson
> Priority: Blocker
> Fix For: 0.20.4, 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.