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

Josh Elser commented on HBASE-19735:
------------------------------------

{quote}Do we want/need this? Unsure if it's intentional or left over from a 
copy/paste from elsewhere.
{quote}
Hrm, looks like it could be dropped. I don't think I've built the site with 
this so it's probably just a no-op directive.
{quote}id mismatch
{quote}
Danke.
{quote}I'm not sure if this will work. The intent is correct, but MR jobs might 
fail without jersey, at least against hadoop 3. Been battling through some of 
the related issues on HBASE-19991.
{quote}
Noted. I'm not sure if [~busbey]'s shaded Hadoop client jars insulate us from 
this for H3 completely (read-as only relevant for h2)? Need to give both h2 and 
h3 some love which I haven't.
{quote}What kind of testing have you done with the resulting artifact?
{quote}
Just some basic stuff with H3:
 * Run a custom {{main}} program that talks to HBase
 * Launch hbase-shell
 * Launch a MR job

Speaking of Sean earlier:
{quote}it'd be nice if this came with a nightly test that made sure the 
resultant client artifact functioned.
{quote}
I do need to circle back around and figure out what the best thing for this 
would be. Should this just be something that can be a part of the standard 
Maven build or something standalone we run with Jenkins? Thoughts?

> Create a minimal "client" tarball installation
> ----------------------------------------------
>
>                 Key: HBASE-19735
>                 URL: https://issues.apache.org/jira/browse/HBASE-19735
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Major
>             Fix For: 3.0.0
>
>         Attachments: HBASE-19735.000.patch, HBASE-19735.001.branch-2.patch, 
> HBASE-19735.002.branch-2.patch, HBASE-19735.003.patch, HBASE-19735.004.patch
>
>
> We're moving ourselves towards more controlled dependencies. A logical next 
> step is to try to do the same for our "binary" artifacts that we create 
> during releases.
> There is code (our's and our dependency's) which the HMaster and RegionServer 
> require which, obviously, clients do not need.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to