[
https://issues.apache.org/jira/browse/MAPREDUCE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12756649#action_12756649
]
Owen O'Malley commented on MAPREDUCE-954:
-----------------------------------------
Thanks Tom, for that. I hadn't seen that syntax for creating nested objects
before.
The use cases you found are indicative of the problem, but it is really wider
than that. The common theme was that the details, especially in the
constructors and fields were far more specific than the interfaces. My goal
with this jira was to protect ourselves from future needs where a copy
constructor is not sufficient. Does that make sense?
> The new interface's Context objects should be interfaces
> --------------------------------------------------------
>
> Key: MAPREDUCE-954
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-954
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: client
> Reporter: Owen O'Malley
> Assignee: Arun C Murthy
> Fix For: 0.21.0
>
> Attachments: MAPREDUCE-954.patch, MAPREDUCE-954.patch,
> MAPREDUCE-954.patch
>
>
> When I was doing HADOOP-1230, I was persuaded to make the Context objects as
> classes. I think that was a serious mistake. It caused a lot of information
> leakage into the public classes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
