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

Posted to dev@hbase.apache.org by "Keegan Witt (JIRA)" <ji...@apache.org> on 2014/08/27 23:00:57 UTC

[jira] [Created] (HBASE-11843) MapReduce classes shouldn't be in hbase-server

Keegan Witt created HBASE-11843:
-----------------------------------

             Summary: MapReduce classes shouldn't be in hbase-server
                 Key: HBASE-11843
                 URL: https://issues.apache.org/jira/browse/HBASE-11843
             Project: HBase
          Issue Type: Bug
          Components: build
            Reporter: Keegan Witt
            Priority: Minor


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-gh5yVUw@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.2#6252)