[
https://issues.apache.org/jira/browse/HADOOP-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14034585#comment-14034585
]
Haohui Mai commented on HADOOP-10389:
-------------------------------------
Thanks [~decster] for the input. This could be another direction to go. Some of
my thoughts:
bq. 1. centos does not have enough support for c+11, c+11 is not generally
available yet
The POC patch uses a few syntactic sugars in c++11, which can be easily
implemented in C++TR1 (Note that the current native code is using
{{std::shared_ptr}} from tr1 already). The tougher part is that the private
APIs passes the {{std::error_code}} objects for error conditions, it can be
fixed by passing int or {{boost::system::error_code}} instead.
bq. 2. remain libhdfs compatibility, since libhdfs is written in c, we might
just continue using c as well
If the ultimate goal is to implement the libhdfs interface, there should be no
c++ symbols exported in the library, thus there is really no compatibility
issue from this regard. As a result, c++ remains as an implementation detail
only.
bq. 1. the protobuf-c library is just not so reliable as official protobuf
library which is maintained and verified by google and many other
companies/projects, I read some of the protobuf-c code, it uses a reflection
style implementation to do serializing/deserializing, so performance, security,
compatibility may all at risk. I see https://github.com/protobuf-c/protobuf-c
only have 92 stars.
I think this is a legit concern. It might be better to depend only on widely
deployed, well-tested libraries.
> Native RPCv9 client
> -------------------
>
> Key: HADOOP-10389
> URL: https://issues.apache.org/jira/browse/HADOOP-10389
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: HADOOP-10388
> Reporter: Binglin Chang
> Assignee: Colin Patrick McCabe
> Attachments: HADOOP-10388.001.patch,
> HADOOP-10389-alternative.000.patch, HADOOP-10389.002.patch,
> HADOOP-10389.004.patch, HADOOP-10389.005.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
