[
https://issues.apache.org/jira/browse/HADOOP-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607768#action_12607768
]
Rob Weltman commented on HADOOP-3479:
-------------------------------------
Pretty-printing tools may be nice but do not replace proper structure in the
document itself, especially if it is going to be edited with an off-the-shelf
tool (XML editor or text editor) or viewed with an off-the-shelf tool (HTML
browser, for example).
I really don't see any advantage to the generic name-value structure over one
that reflects the semantics of the content. If it is a matter of this release
or the next one and the decision is time-based, it could be that hierarchical
organization has to slip to the next release. There is a risk that initial
decisions stick, though. It isn't necessarily the case that "there will always
be time to redo this later".
If the proposal is to switch to hierarchical structure when HADOOP-3579 is
addressed, maybe that is the right compromise.
> 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.1.patch, 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.
