[
https://issues.apache.org/jira/browse/HBASE-21153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603908#comment-16603908
]
stack commented on HBASE-21153:
-------------------------------
Dunno. I was using another script of your writing that does 'hbase version'...
that worked in hbase-2.0.x but fails in hbase-2.1.x. Does this script even go
into the client tarball? When I do 'hbase version' after removing "version"
then there is no shaded jar set made and we fall through to use the old jars.
There is no hbase-common in shaded client jar? Or should we be using different
VersionInfo class when we run? I looked for a VersionInfo in the shaded client
jar but didn't find one.
> hbase version broke in 2.1+
> ---------------------------
>
> Key: HBASE-21153
> URL: https://issues.apache.org/jira/browse/HBASE-21153
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.1.0
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 2.1.1
>
>
> When I run the {{hbase version}} command it comes back with:
> {code}$ ./bin/hbase version
> Error: Could not find or load main class
> org.apache.hadoop.hbase.util.GetJavaProperty
> Error: Could not find or load main class
> org.apache.hadoop.hbase.util.VersionInfo{code}
> The two classes are in hbase-commons.
> The nice shaded refactoring of our bin/hbase -- i.e. using shaded jars
> wherever possible -- may have overstretched expecting version to work with
> shaded client ([~busbey] ?). If so, fix is < one-liner.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
