You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2014/12/19 02:11:14 UTC

[jira] [Reopened] (ACCUMULO-1880) Separate mapreduce into its own module

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

Josh Elser reopened ACCUMULO-1880:
----------------------------------
      Assignee:     (was: Mike Drob)

Reopening because ACCUMULO-3402 reverted the changes here.

We're all still in agreement that we could do something different, but the original approach wasn't sufficient.

> Separate mapreduce into its own module
> --------------------------------------
>
>                 Key: ACCUMULO-1880
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1880
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: client
>            Reporter: Mike Drob
>             Fix For: 1.7.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> It would be nice to have the mapreduce bindings be a separate module, so that users wanting to run MR jobs could have a more minimal set of dependencies to compile against.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)