Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <645250324.274621266225327967.JavaMail.jira@brutus.apache.org>
Date: Mon, 15 Feb 2010 09:15:27 +0000 (UTC)
From: "ryan rawson (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2219) stop using code mapping for method
 names in the RPC
In-Reply-To: <268569578.229451265968587917.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

rerunning, might be facing system variance, eg: chrome messing with the run

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