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

Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2015/01/30 17:46:34 UTC

[jira] [Commented] (HBASE-12946) Decouple MapReduce pieces from hbase-server

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

stack commented on HBASE-12946:
-------------------------------

Yes. We've talked of doing this for a long time.  I was hoping the new API would make this effort easier to do.

> Decouple MapReduce pieces from hbase-server
> -------------------------------------------
>
>                 Key: HBASE-12946
>                 URL: https://issues.apache.org/jira/browse/HBASE-12946
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Lars Francke
>
> I could not find an existing issue for this.
> This has come up multiple times publicly:
> * http://comments.gmane.org/gmane.comp.java.hadoop.hbase.user/41916
> * http://gbif.blogspot.de/2014/11/upgrading-our-cluster-from-cdh4-to-cdh5.html
> It'd be great if we could either move the mapreduce pieces to hbase-client or get a hbase-mapreduce component. Some things seem easy to decouple others not so much.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)