[
https://issues.apache.org/jira/browse/HADOOP-3822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618301#action_12618301
]
Steve Loughran commented on HADOOP-3822:
----------------------------------------
In Open Source there is no way to stop anyone getting at your internals. What
you can do is flag which interfaces or classes have no stability guarantees.
People are free to work with them -subclass the classes, implement the
interfaces- but it is not the hadoop team's concerns if a new release stops
their thing from recompiling.
Interfaces can be easier to mock, and easier to patch in to other object
hierarchies -and there is no requirement to never change an interface. Its
something that sun and joshua do for the sun libraries, but even they have
internal stuff they don't like you touching and which moves about from time to
time.
This is why the idea of having an @Internal tag appeals to me -something you
can put on an interface to say "this is internal, track SVN Head if you don't
want to be surprised".
> 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.
