[ https://issues.apache.org/jira/browse/HBASE-20615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487692#comment-16487692 ]
Sean Busbey commented on HBASE-20615: ------------------------------------- we had previously yes. I think that decision is wrong, especially if the push post HBase 2 is going to be towards folks using the shaded clients. 1) If most applications are going to use the shaded clients, then by not shipping them we're encouraging a situation where you end up with a copy per application. 2) If we ship them we can simplify the default path for some uses, namely making {{hbase mapredcp}} return the shaded mapreduce client. Similarly, we could make a "client classpath" command that gave the shaded artifact as an alternative to the current bloat in the {{hbase classpath}} > 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)