[
https://issues.apache.org/jira/browse/HADOOP-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606494#action_12606494
]
Doug Cutting commented on HADOOP-3479:
--------------------------------------
This new class unfortunately duplicates a lot of code from Configuration. We
need more configuration classes, but rather fewer. Long-term we should get rid
of JobConf, and replace it with, e.g., setter and getter methods on a Job
class, where Job has a Configuration field and does not subclass Configuration.
It also seems to me that your needs here could be met with the existing
Configuration, by either:
- a separate config file per queue; and/or
- a property-naming convention, e.g., queue.default.allowed-users, for the
"default" queue.
If you need a list of all queues, you could either scan, or add a property that
lists queue names.
This might not be optimal, but it would be functional. Revamping Configuration
should not be done by a proliferation of new, incompatible configuration
mechanisms, but rather by enhancing or replacing the existing mechanism.
> 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.
