Sean Busbey updated HBASE-20615:
      Resolution: Fixed
    Release Note: 
<!-- markdown -->

HBase's built in scripts now rely on the downstream facing shaded artifacts 
where possible. In particular interest to downstream users, the `hadoop 
classpath` and `hadoop mapredcp` commands now return the relevant shaded client 
artifact and only those third paty jars needed to make use of them (e.g. 
slf4j-api, commons-logging, htrace, etc).

Downstream users should note that by default the `hbase classpath` command will 
treat having `hadoop` on the shell's PATH as an implicit request to include the 
output of the `hadoop classpath` command in the returned classpath. This 
long-existing behavior can be opted out of by setting the environment variable 
`HBASE_DISABLE_HADOOP_CLASSPATH_LOOKUP` to the value "true". For example: 
`HBASE_DISABLE_HADOOP_CLASSPATH_LOOKUP="true" bin/hbase classpath`.
          Status: Resolved  (was: Patch Available)

pushed to master and branch-2. I missed signed-off-by lines on master. :/

> 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

Reply via email to