hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3479) Implement configuration items useful for Hadoop resource manager (v1)
Date Fri, 20 Jun 2008 20:17:45 GMT

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

Doug Cutting commented on HADOOP-3479:

> by limiting the new code to a separate class, and the new configuration to a separate
file, we isolate ourselves against too many changes to code in the future

Yes, but at a high cost.  Not only is code duplicated, but a new public API is added.  New
public APIs should only be added when we intend to support them long-term.  If you want to
implement something short-term, then it ought to be package-private, located with the rest
of your implementation, not grouped with other generic, public configuration APIs.

Until HADOOP-3579 is resolved, I would prefer an approach that leverages the existing Configuration
mechanism, perhaps with minor modifications if needed.  (For example, one might reasonably
wish to be able to create a Configuration from a file without reading hadoop-default.xml and

> 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.

View raw message