[
https://issues.apache.org/jira/browse/HADOOP-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617775#action_12617775
]
Steve Loughran commented on HADOOP-3822:
----------------------------------------
You don't need to freeze interfaces. You only need to freeze interfaces that
you promise to keep stable :)
There's one other risk with abstract classes -that the base class adds a new
public or protected method that accidentally clashes with one a subclass has
implemented, in which case the subclass one gets used. There are some checks in
C# to catch this, but not java, not even with the @Override attribute, because
that attribute is optional.
The best way to avoid problems is to have people building and testing their
code with your SVN_HEAD version, as it finds problems the minute they are
checked in, rather than when a release occurs. This is something we can do in
open source development, across teams and organisations.
> 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.
