Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 29 Oct 2015 23:44:27 +0000 (UTC)
From: "James Clampffer (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12895231.1442863471000.102379.1446162267786@Atlassian.JIRA>
In-Reply-To: <JIRA.12895231.1442863471000@Atlassian.JIRA>
References: <JIRA.12895231.1442863471000@Atlassian.JIRA>
 <JIRA.12895231.1442863471409@arcas>
Subject: [jira] [Commented] (HDFS-9117) Config file reader / options classes
 for libhdfs++
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-9117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981582#comment-14981582 ] 

James Clampffer commented on HDFS-9117:
---------------------------------------

"The principle is that the C++ APIs should be able to solely rely on the Options class for all configurations. The class is strongly-typed and has clear schema. From the dependency point of view there are strong desires and use cases that running libhdfspp without depending XML configuration. I'll be -1 if the C++ APIs are bundled with XML configurations."

I just want to clarify, when you say the C++ APIs do you mean the lower level wire protocol and continuation stuff currently living mostly in /fs and /reader?  Or does this also include the FileHandle/HadoopFileSystem objects that were added with the C API but are useful on their own?

>From my point of view I think it's useful to be able to use this from the HadoopFileSystem object.  I'm working on retry stuff now and I'd like to be able to pull in values for things like time to reset the DN errors from a configuration object.  From an application level or user point of view I think it's important to be able to do this:

HadoopFileSystem *myfs = new HadoopFileSystem(some_configuration_object)

> Config file reader / options classes for libhdfs++
> --------------------------------------------------
>
>                 Key: HDFS-9117
>                 URL: https://issues.apache.org/jira/browse/HDFS-9117
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: hdfs-client
>    Affects Versions: HDFS-8707
>            Reporter: Bob Hansen
>            Assignee: Bob Hansen
>         Attachments: HDFS-9117.HDFS-8707.001.patch, HDFS-9117.HDFS-8707.002.patch, HDFS-9117.HDFS-8707.003.patch, HDFS-9117.HDFS-8707.004.patch, HDFS-9117.HDFS-8707.005.patch, HDFS-9117.HDFS-8707.006.patch, HDFS-9117.HDFS-8707.008.patch, HDFS-9117.HDFS-8707.009.patch, HDFS-9117.HDFS-8707.010.patch, HDFS-9117.HDFS-9288.007.patch
>
>
> For environmental compatability with HDFS installations, libhdfs++ should be able to read the configurations from Hadoop XML files and behave in line with the Java implementation.
> Most notably, machine names and ports should be readable from Hadoop XML configuration files.
> Similarly, an internal Options architecture for libhdfs++ should be developed to efficiently transport the configuration information within the system.


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