[
https://issues.apache.org/jira/browse/HBASE-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-11843.
---------------------------
Resolution: Duplicate
Resolving as duplicate of HBASE-18640 "Move mapreduce out of hbase-server into
separate module" though HBASE-18640 came later.
This issue had great subtasks that I moved out as standalone. They are linked
here.
> MapReduce classes shouldn't be in hbase-server
> ----------------------------------------------
>
> Key: HBASE-11843
> URL: https://issues.apache.org/jira/browse/HBASE-11843
> Project: HBase
> Issue Type: Improvement
> Components: build
> Reporter: Keegan Witt
> Assignee: Nate Edel
> Priority: Critical
> Fix For: 2.0.0
>
>
> I'm opening this to continue the discussion I started a while back:
> http://mail-archives.apache.org/mod_mbox/hbase-user/201405.mbox/%3ccamuu0w_xooxeg779rrfjturau+uxeavunzxkw9dxfo-gh5y...@mail.gmail.com%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).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
