hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-954) The new interface's Context objects should be interfaces
Date Wed, 16 Sep 2009 08:19:58 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun C Murthy updated MAPREDUCE-954:
------------------------------------

    Attachment: MAPREDUCE-954.patch

Here is a nearly complete patch for illustrative purposes.

I've had to resort to composition in {Mapper|Reducer}Impl.Context to include a member {Map|Reduce}ContextImpl
to get around the fact that {Mapper|Reducer}.Context is an abstract class, thus resulting
in the inability to get {Mapper|Reducer}Impl.Context to extend both  {Mapper|Reducer}.Context
and {Map|Reduce}ContextImpl (MI).

> 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
>
>
> 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.


Mime
View raw message