[
https://issues.apache.org/jira/browse/HBASE-7233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511196#comment-13511196
]
Matt Corgan commented on HBASE-7233:
------------------------------------
few thoughts:
- we can make a KEY_VALUE encoder that serializes cells in the current wire
format which is pretty simple for other languages to parse. it can be a
slightly more performant fallback than per-field protocol buffers
- encoders will have to be backwards compatible for a while on the server
anyway because people have lots of hfiles encoded with them
- encoders could have versions, but they are also pretty intricate, so any
changes might merit a whole new encoder like FAST_DIFF2
- the client could pass a short list of encoder options in decending order of
preference like FAST_DIFF2, KEY_VALUE, PB, where PB is the forever-supported
fallback
I'm a little skeptical that this will be the last client hbase ever supports.
If something really major changes, we could make a whole new client and the
server could translate things to support the old client.
> Serializing KeyValues when passing them over RPC
> ------------------------------------------------
>
> Key: HBASE-7233
> URL: https://issues.apache.org/jira/browse/HBASE-7233
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Attachments: 7233.txt, 7233-v2.txt
>
>
> Undo KeyValue being a Writable.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira