[ACCUMULO-1880] Separate mapreduce into its own module

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: client
• Assignee: Unassigned
• Reporter: Mike Drob
• Created: 11/Nov/13 18:05
• Updated: 13/Jan/17 18:21
• Resolved: 15/Jan/15 22:51

Description

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.

Issue Links

• breaks: ACCUMULO-3402 Introduction of the mapreduce maven module breaks 1.6 compatibility
• is blocked by: ACCUMULO-2702 Decouple subclasses of ClientOpts from MapReduce Configurations
• is related to: ACCUMULO-2829 tool.sh doesn't include new mapreduce jar in libjars
• is related to: ACCUMULO-4569 Create separate mapreduce module
• is required by: ACCUMULO-1242 Consistent logging

Sub-Tasks

• tool.sh doesn't include new mapreduce jar in libjars: Resolved
• Introduction of the mapreduce maven module breaks 1.6 compatibility: Resolved