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

ASF GitHub Bot commented on METAMODEL-93:
-----------------------------------------

GitHub user tomaszguzialek opened a pull request:

    https://github.com/apache/metamodel/pull/12

    Upgrading hbase-client to 1.0.0 and downgrading Guava to 16.0

    Issue: METAMODEL-93.
    
    Tested on Ubuntu 14.04.2 with HBase 1.0.0 installed.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tomaszguzialek/metamodel hbase-1.0.0

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metamodel/pull/12.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #12
    
----
commit e95f36e6c43fafec301747ff506cce9b966ca533
Author: tomaszguzialek <[email protected]>
Date:   2015-03-28T22:07:12Z

    Upgrading hbase-client to 1.0.0 and downgrading Guava to 16.0

----


> Upgrade HBase dependency to support Hadoop 2
> --------------------------------------------
>
>                 Key: METAMODEL-93
>                 URL: https://issues.apache.org/jira/browse/METAMODEL-93
>             Project: Apache MetaModel
>          Issue Type: Improvement
>    Affects Versions: 4.3.0-incubating
>         Environment: Cloudera CDH 5.1.0
>            Reporter: Tomasz Guzialek
>              Labels: hadoop
>
> Current hbase-client dependency version in HBase module is 0.95.1-hadoop1. We 
> should consider upgrading our depedency to support Hadoop 2.
> I tried to connect to HBase in Cloudera's Quickstart VM with CDH 5.1.0 from 
> MetaModel, but it is using HBase 0.98.1 (Hadoop 2). I guess, many people 
> start with this popular distribution for a proof of concept, so ensuring that 
> MetaModel can connect to HBase on Hadoop 2 is important. 



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

Reply via email to