[
https://issues.apache.org/jira/browse/HBASE-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey updated HBASE-20334:
--------------------------------
Status: Patch Available (was: In Progress)
v1
- rebased master + patches for HBASE-20332, HBASE-20333, HBASE-19735, and
HBASE-20615
- adds a support script for automating caching apache project artifacts
- updates Jenkinsfile to use said caching script ot get a copy of hadoop 2
and hadoop 3
- updates our "source tarball" test to be general "packaging and integration
with Hadoop"
- adds use of test script with hadoop 2, hadoop 3, and hadoop 3 w/hadoop's
client artifacts
- updated handling of args to the test script so that we work with relative
paths
- updated for feedback from v0: does file checks for passed jars.
> add a test that expressly uses both our shaded client and the one from hadoop
> 3
> -------------------------------------------------------------------------------
>
> Key: HBASE-20334
> URL: https://issues.apache.org/jira/browse/HBASE-20334
> Project: HBase
> Issue Type: Sub-task
> Components: hadoop3, shading
> Affects Versions: 2.0.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Major
> Attachments: HBASE-20334.0.patch, HBASE-20334.1.patch
>
>
> Since we're making a shaded client that bleed out of our namespace and into
> Hadoop's, we should ensure that we can show our clients coexisting. Even if
> it's just an IT that successfully talks to both us and HDFS via our
> respective shaded clients, that'd be a big help in keeping us proactive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
