[ 
https://issues.apache.org/jira/browse/HADOOP-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604809#action_12604809
 ] 

Steve Loughran commented on HADOOP-3479:
----------------------------------------

As someone whose product does configuration and deployment, this is somehting 
that I do feel strongly about.

While I like hierarchical representations, I dont think XPath should be used 
unless everyone understand the consequences. For example, what happens if more 
than one thing comes back? What happens if someone plays xml namespace games. I 
have tried to use XPath based configuration schemas and it soon gets complex. 
What if I want to do property expansion in the Path, like 
/configuration/queues/[EMAIL PROTECTED]"${user.name}"] ? what if I set a path 
that exists -is that an append or an overwrite?

Equally importantly, it forces a requirement for the XML DOM to be the only 
representation of content. That is a tree, not a graph, and not that agile. If 
you were to use LDAP or anything else then things wouldnt work. 

So . I'm:
+1 for a consistent way of configuring things. 
+1 for hierarchical representation of information. 
+1 for decoupling the configuration source from the Configuration class, so 
that any provider of a hierarchical configuration name-value pairs can return 
values on name lookups. 
-1 for XPath



> Implement configuration items useful for Hadoop resource manager (v1)
> ---------------------------------------------------------------------
>
>                 Key: HADOOP-3479
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3479
>             Project: Hadoop Core
>          Issue Type: New Feature
>            Reporter: Hemanth Yamijala
>            Assignee: Hemanth Yamijala
>         Attachments: 3479.patch
>
>
> HADOOP-3421 lists requirements for a new resource manager for Hadoop. 
> Implementation for these will require support for new configuration items in 
> Hadoop. This JIRA is to define such configuration, and track it's 
> implementation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to