GitHub user dkhwangbo opened a pull request:
https://github.com/apache/tajo/pull/915
TAJO-2025: HBASE_LIB/metrics-core-*.jar should be included in CLASSPATH
When I try to connect HBase client via TAJO, TAJO cannot connect HBase with
below logs.
```
INFO org.apache.hadoop.hbase.client.RpcRetryingCaller: Call exception,
tries=10, retries=35, retryTime=68306ms, msg=row 'lineitem,,' on table
'hbase:meta' at region=hbase:meta,,1.1588230740,
hostname=<address>,60020,1450062494778, seqNum=0
INFO org.apache.hadoop.hbase.client.RpcRetryingCaller: Call exception,
tries=11, retries=35, retryTime=88389ms, msg=row 'lineitem,,' on table
'hbase:meta' at region=hbase:meta,,1.1588230740,
hostname=<address>,60020,1450062494778, seqNum=0
...
org.apache.hadoop.hbase.client.RpcRetryingCaller@5b5e2d4c,
java.io.IOException: com.google.protobuf.ServiceException:
java.lang.NoClassDefFoundError: com/yammer/metrics/core/Gauge
```
But, I can connect HBase using ```TestHBaseTable```.
I found out that tsql can connect hbase client with appending
```HBASE_LIB/HBase-hadoop2-compat-*.jar``` to classpath in ```bin/tajo```.
But, ```HBase-hadoop2-compat-*.jar``` has lots of dependency so I try to
find out necessity for TAJO in this jar.
```HBASE_LIB/metrics-core-*.jar``` is answer.
I test hbase 0.98.16.1-hadoop2 version with TAJO, builded with
manually-configured Hbase version.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dkhwangbo/tajo TAJO-2025
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/915.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 #915
----
commit 8a89556555814b15adcbb20df44f4e9146368d96
Author: Dongkyu Hwangbo <[email protected]>
Date: 2015-12-17T03:29:35Z
initial commit
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
