[ https://issues.apache.org/jira/browse/HDFS-10787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15459611#comment-15459611 ]
Bob Hansen commented on HDFS-10787: ----------------------------------- For the sake of simplicity, I think we should introduce a public facade for them that only exposes two functions: LoadConfigs() and LoadConfigsFromDirectory(const char * dir), each returning an Options object. Do we have a compelling use case for more than that? Anything that wants to poke values in can poke values into the returned Options rather than the XML, I think. > libhdfs++: hdfs_configuration and configuration_loader should be accessible > from our public API > ----------------------------------------------------------------------------------------------- > > Key: HDFS-10787 > URL: https://issues.apache.org/jira/browse/HDFS-10787 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: hdfs-client > Reporter: Anatoli Shein > > Currently, libhdfspp examples and tools all have this: > #include "hdfspp/hdfspp.h" > #include "common/hdfs_configuration.h" > #include "common/configuration_loader.h" > This is done in order to read configs and connect. We want > hdfs_configuration and configuration_loader to be accessible just by > including our hdfspp.h. One way to achieve that would be to create a builder, > and would include the above libraries. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org