hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2219) stop using code mapping for method names in the RPC
Date Fri, 12 Mar 2010 20:55:27 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

stack updated HBASE-2219:

      Resolution: Fixed
    Hadoop Flags: [Incompatible change, Reviewed]  (was: [Incompatible change])
          Status: Resolved  (was: Patch Available)

Committed to branch.

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

View raw message