You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2015/01/10 02:53:34 UTC

[jira] [Resolved] (HBASE-4924) More issues running hbase on hadoop 0.23

     [ https://issues.apache.org/jira/browse/HBASE-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-4924.
-----------------------------------
    Resolution: Won't Fix

Yeah we don't care about this now

> More issues running hbase on hadoop 0.23
> ----------------------------------------
>
>                 Key: HBASE-4924
>                 URL: https://issues.apache.org/jira/browse/HBASE-4924
>             Project: HBase
>          Issue Type: Bug
>            Reporter: stack
>              Labels: delete
>
> From Roman:
> {code}
> >  3. This is a little bit more sinister and it is not clear what
> >  the resolution path here is. When compiled against .23
> >  the MiniMRCluster dependency latches onto artifact
> >  hadoop-mapreduce/test. There are 2 problems with that:
> >    1. this works only accidentally (but as long as it does
> >    may be it is fine) since we don't have an explicit
> >    dependency on hadoop-mapreduce test artifact (nor
> >    should we, I think!).
> >
> >    2. MiniMRCluster from there is soon to be deprecated
> >    (MAPREDUCE-3169) ans HBaseTestingUtility should
> >    really transition onto using MiniMRClientClusterFactory
> >    to get a MiniMRCluster.
> {code}
> I think there already an issue for #2 above (courtesy of Andrew IIRC).  We should fix #1 too.



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