You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yechao Chen (JIRA)" <ji...@apache.org> on 2018/09/13 08:33:00 UTC
[jira] [Commented] (HBASE-20615) emphasize use of shaded client
jars when they're present in an install
[ https://issues.apache.org/jira/browse/HBASE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16613194#comment-16613194 ]
Yechao Chen commented on HBASE-20615:
-------------------------------------
hbase classpath
will print
Error: Could not find or load main class org.apache.hadoop.hbase.util.GetJavaProperty
before 2.1, bin/hbase
"HADOOP_IN_PATH=$(PATH="${HADOOP_HOME:-${HADOOP_PREFIX}}/bin:$PATH" which hadoop 2>/dev/null)"
after 2.1,the " 2>/dev/null" was removed
> emphasize use of shaded client jars when they're present in an install
> ----------------------------------------------------------------------
>
> Key: HBASE-20615
> URL: https://issues.apache.org/jira/browse/HBASE-20615
> Project: HBase
> Issue Type: Sub-task
> Components: build, Client, Usability
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
> Fix For: 3.0.0, 2.1.0
>
> Attachments: HBASE-20615.0.patch, HBASE-20615.1.patch, HBASE-20615.2.patch
>
>
> Working through setting up an IT for our shaded artifacts in HBASE-20334 makes our lack of packaging seem like an oversight. While I could work around by pulling the shaded clients out of whatever build process built the convenience binary that we're trying to test, it seems v awkward.
> After reflecting on it more, it makes more sense to me for there to be a common place in the install that folks running jobs against the cluster can rely on. If they need to run without a full hbase install, that should still work fine via e.g. grabbing from the maven repo.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)