[ https://issues.apache.org/jira/browse/HADOOP-10388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925585#comment-13925585 ]
Binglin Chang commented on HADOOP-10388: ---------------------------------------- About coding standard, google is mostly fine. I mention c+\+11 mostly for the new std libraries(thread, lock/condition, random, unique_ptr/shared_ptr, regex), so we can avoid writing lot of common utility code, it's fine we use boost instead, and provide typedefs so c+\+11 or boost can both be an option, old compiler can use boost instead, new compiler can avoid boost dependency. Agree with Colin, I tend to avoid using "fancy" language features such as lambda, template, std::function. For compatibility the code should be plain simple, especially for public api, c+\+ does not have good binary compatibility(mainly virtual method) issue, so we need to be careful. > Pure native hadoop client > ------------------------- > > Key: HADOOP-10388 > URL: https://issues.apache.org/jira/browse/HADOOP-10388 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Binglin Chang > > A pure native hadoop client has following use case/advantages: > 1. writing Yarn applications using c++ > 2. direct access to HDFS, without extra proxy overhead, comparing to web/nfs > interface. > 3. wrap native library to support more languages, e.g. python > 4. lightweight, small footprint compare to several hundred MB of JDK and > hadoop library with various dependencies. -- This message was sent by Atlassian JIRA (v6.2#6252)