[ https://issues.apache.org/jira/browse/HBASE-20334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16509063#comment-16509063 ]
Sean Busbey commented on HBASE-20334: ------------------------------------- Here's v1 running in a nightly branch: https://builds.apache.org/blue/organizations/jenkins/HBase%20Nightly/detail/HBASE-20331/43/pipeline/100 and here's the output logs of each of the three configurations that are tested: https://builds.apache.org/job/HBase%20Nightly/job/HBASE-20331/43/artifact/output-integration/ > 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)