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

Colin Patrick McCabe updated HDFS-7207:
---------------------------------------
    Description: We should consider adding a C\+\+ interface for libhdfs, 
libhdfs3, and libwebhdfs.  This interface should not impose unreasonable 
compatibility constraints on the libraries, and should be useful for many C\+\+ 
projects in order to be useful.  We may also want to avoid exceptions because 
some C\+\+ clients do not use them.  (was: There are three major disadvantages 
of exposing exceptions in the public API:

* Exposing exceptions in public APIs forces the downstream users to be compiled 
with {{-fexceptions}}, which might be infeasible in many use cases.
* It forces other bindings to properly handle all C++ exceptions, which might 
be infeasible especially when the binding is generated by tools like SWIG.
* It forces the downstream users to properly handle all C++ exceptions, which 
can be cumbersome as in certain cases it will lead to undefined behavior (e.g., 
throwing an exception in a destructor is undefined.)

)
       Priority: Major  (was: Blocker)
     Issue Type: Improvement  (was: Bug)

> Consider adding a C++ API for libhdfs, libhdfs3, and libwebhdfs
> ---------------------------------------------------------------
>
>                 Key: HDFS-7207
>                 URL: https://issues.apache.org/jira/browse/HDFS-7207
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Haohui Mai
>            Assignee: Colin Patrick McCabe
>         Attachments: HDFS-7207.001.patch
>
>
> We should consider adding a C\+\+ interface for libhdfs, libhdfs3, and 
> libwebhdfs.  This interface should not impose unreasonable compatibility 
> constraints on the libraries, and should be useful for many C\+\+ projects in 
> order to be useful.  We may also want to avoid exceptions because some C\+\+ 
> clients do not use them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to