[
https://issues.apache.org/jira/browse/MAPREDUCE-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philip Zeyliger updated MAPREDUCE-2043:
---------------------------------------
Attachment: MAPREDUCE-2043.patch.txt
Chris and Luke,
Thanks for the context. I think the experimental developers ought to
embed/extend Hadoop in a different package than org.apache.hadoop.mapred, so
there's a reasonable argument for 'public', with the interface caveats. Agree
wholeheartedly that this interface should be evolving. It's proven a
convenient way, actually, to try some things out.
I've taken Luke's suggestion and added the interface annotations. I've
"tested" this with "ant compile-core" only (ant compile breaks on mumak in
contrib). Attached is that new patch.
-- Philip
> TaskTrackerInstrumentation and JobTrackerInstrumentation should be public
> -------------------------------------------------------------------------
>
> Key: MAPREDUCE-2043
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2043
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: tasktracker
> Affects Versions: 0.22.0
> Reporter: Philip Zeyliger
> Assignee: Philip Zeyliger
> Attachments: MAPREDUCE-2043.patch.txt, MAPREDUCE-2043.patch.txt
>
>
> Hadoop administrators can specify classes to be loaded as
> "TaskTrackerInstrumentation" and "JobTrackerInstrumentation" implementations,
> which, roughly, define listeners on TT and JT events. Unfortunately, since
> the class has default access, extending it requires setting the extension's
> package to org.apache.hadoop.mapred, which seems like poor form.
> I propose we make the two instrumentation classes public, so they can be
> extended wherever.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
