[HBASE-11843] MapReduce classes shouldn't be in hbase-server

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Fix Version/s: 2.0.0
• Component/s: build
• Assignee: Unassigned
• Reporter: Keegan Witt
• Created: 27/Aug/14 20:59
• Updated: 17/Jun/22 17:20
• Resolved: 21/Sep/17 05:02

Description

I'm opening this to continue the discussion I started a while back: http://mail-archives.apache.org/mod_mbox/hbase-user/201405.mbox/[e-mail]%3E.

To summarize, I think the MapReduce classes used by clients (like TableMapper, TableReducer, etc) don't belong in hbase-server. This forces the user to pull in a rather large artifact for a relatively small number of classes. These should either be put in hbase-client, or possibly an artifact of their own (like the hbase-mapreduce idea Enis suggested).

Issue Links

• duplicates: HBASE-18640 Move mapreduce out of hbase-server into separate hbase-mapreduce module
• is duplicated by: HBASE-12946 Decouple MapReduce pieces from hbase-server
• is related to: HBASE-14911 Move functionality needed to write HFiles without RegionServer dependency
• is related to: HBASE-14912 Move functionality needed to read WAL without RegionServer dependency
• is related to: HBASE-14913 Enable testing I/O without regionserver or threads.
• is related to: HBASE-14914 Move functionality needed to handle Snapshots without RegionServer dependency
• relates to: HBASE-13992 Integrate SparkOnHBase into HBase

Sub-Tasks

• Create base hbase-mapred and hbase-io modules, move HTableInputFormat and HTableOutputFormat: Closed