hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nate Edel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-11843) MapReduce classes shouldn't be in hbase-server
Date Wed, 02 Dec 2015 19:38:11 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15036441#comment-15036441

Nate Edel commented on HBASE-11843:

This is looking bigger, and probably difficult to review especially coming from a relative
newb.  I've broken things up into subtasks, and this should be easier to review.

> 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-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

View raw message