hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-1638) Divide MapReduce into API and implementation source trees
Date Thu, 16 Jun 2011 21:42:47 GMT

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

Tom White updated MAPREDUCE-1638:
---------------------------------

    Attachment: MAPREDUCE-1638.patch

This patch just does some more clean up to allow the separation to happen. This part can be
committed now, while the actual separation of the trees would be done later, probably as a
part of the process of getting MR-279 into trunk.

> Divide MapReduce into API and implementation source trees
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-1638
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1638
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: build, client
>            Reporter: Tom White
>            Assignee: Tom White
>         Attachments: MAPREDUCE-1638.patch, MAPREDUCE-1638.patch, MAPREDUCE-1638.sh
>
>
> I think it makes sense to separate the MapReduce source into public API and implementation
trees. The public API could be broken further into kernel and library trees.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message