[
https://issues.apache.org/jira/browse/HADOOP-3579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605555#action_12605555
]
Steve Loughran commented on HADOOP-3579:
----------------------------------------
I think there is a serious risk of painting yourself into a corner by defining
your own hierarchical configuration and cross-referencing model, without
discovering the consequences of your actions. There are issues like overidding,
merging, and default values to consider here, as well as that of allowing
external tools to manage hadoop clusters.
Can we start by enumerating what the needs are here, before building any
solutions. I think for this use case it is
* Allow multiple aspects of hadoop to be instantiated (here queues) each with
custom configuration options.
* Provide an API for retrieving the specific configuration parameters for a
specific instance
* Provide a means in the configuration files of cross-referencing one
instance's configuration parameters in another.
Is that it?
> Support property groups in Hadoop configuration
> -----------------------------------------------
>
> Key: HADOOP-3579
> URL: https://issues.apache.org/jira/browse/HADOOP-3579
> Project: Hadoop Core
> Issue Type: Improvement
> Components: conf
> Reporter: Hemanth Yamijala
>
> Hadoop configuration is currently a list of key and value pairs. There are
> some use-cases to support configuring groups of related properties. There
> could also be multiple instances of such groups. The issue is for adding
> support for such configuration.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
