[
https://issues.apache.org/jira/browse/HBASE-11843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14113495#comment-14113495
]
Elliott Clark commented on HBASE-11843:
---------------------------------------
[~enis] That was my thought too when I last looked at how to do this. HLog
seemed like the hardest part of those. And HFile and Store are pretty
intertwined so I gave up last time I started looking at this.
It's not a small undertaking but it will pay dividends for the end user. So
totally a worth wile thing to do. Let me know if there's something I can do to
help.
> 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
>
> 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.2#6252)
