hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (MAPREDUCE-1638) Divide MapReduce into API and implementation source trees
Date Thu, 01 Apr 2010 16:00:29 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852427#action_12852427
] 

Steve Loughran commented on MAPREDUCE-1638:
-------------------------------------------

I know of people who are looking at alternate execution engines to the JT, so having that
bit of the API decoupled from the implementation would be good. I don't (yet) see the need
for separate JARs though, it only complicates things and creates new problems.

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message