[jira] [Commented] (HBASE-20615) include shaded artifacts in binary install

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser commented on HBASE-20615:
------------------------------------

Trying to run through this in my head now:
 # Patch here puts HBase shaded jars (including new byo-hadoop variant) in our bin-tarball
 # client-tarball (the WIP one) could eventually also (instead of?) pick up these HBase shaded jars
 # HBASE-20334 gets us 95% of the way to validating that the client-tarball actually works (don't think we need to complicate things here further though)

Is that what you're thinking as well, Sean?

> include shaded artifacts in binary 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
>
>
> 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)