[
https://issues.apache.org/jira/browse/HBASE-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705356#action_12705356
]
Chad Walters commented on HBASE-794:
------------------------------------
Re 1: Agreed with Andrew -- not a good way to go
Re 2 and 4: Looking at the test code at
http://code.google.com/p/thrift-protobuf-compare it' clear the TBinaryProtocol
was used for the tests, not TCompactBinaryProtocol. They also used
TIOStreamTransport -- can't speak to the quality of this transport one way or
another although I gotta think that wrapping it with TFramedTransport would
likely reduce some overhead.
Re 3: No idea. I gotta imagine that some work is needed here since the Java
stuff is less mature than the C++ stuff. Is Bryan watching this ticket? He's
the guy to ask for sure.
Re 5: We should look at where we really want nulls and see if this is too
onerous.
Re 6: Let's please not go down the route of custom RPC -- let's leverage
something reasonable such that the RPC isn't really part of the problem.
> Language neutral IPC as a first class component of HBase architecture
> ---------------------------------------------------------------------
>
> Key: HBASE-794
> URL: https://issues.apache.org/jira/browse/HBASE-794
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client, ipc, master, regionserver
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
>
> This issue considers making a language neutral IPC mechanism and wire format
> a first class component of HBase architecture. Clients could talk to the
> master and regionserver using this protocol instead of HRPC at their option.
> Options for language neutral IPC include:
> * Thrift: http://incubator.apache.org/thrift/
> * Protocol buffers: http://code.google.com/p/protobuf/
> * XDR: http://en.wikipedia.org/wiki/External_Data_Representation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.