[
https://issues.apache.org/jira/browse/HADOOP-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617897#action_12617897
]
Doug Cutting commented on HADOOP-3822:
--------------------------------------
> You don't need to freeze interfaces. You only need to freeze interfaces that
> you promise to keep stable :)
Right. For example, we use interfaces for RPC protocols, but those are not for
public consumption and are only used internally. We do not intend to support
clients or servers that are not in Hadoop's source tree.
So do we intend to permit implementations of the scheduler that are not in
Hadoop's source tree? If so, then we should not use interfaces. If not, then
interfaces are fine, since we can update all implementations if/when we alter
the interface.
> Create a public scheduler API
> -----------------------------
>
> Key: HADOOP-3822
> URL: https://issues.apache.org/jira/browse/HADOOP-3822
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> Reporter: Tom White
> Fix For: 0.19.0
>
> Attachments: hadoop-3822.patch, hadoop-3822.sh
>
>
> The work in HADOOP-3412 provided an API to support pluggable schedulers.
> However implementations have to be in the org.apache.hadoop.mapred package,
> which is undesirable. The goal of this issue is to create a public API for
> scheduler writers to code against.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
