hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-20333) break up shaded client into one with no Hadoop and one that's standalone
Date Tue, 03 Apr 2018 15:18:00 GMT
Sean Busbey created HBASE-20333:

             Summary: break up shaded client into one with no Hadoop and one that's standalone
                 Key: HBASE-20333
                 URL: https://issues.apache.org/jira/browse/HBASE-20333
             Project: HBase
          Issue Type: Sub-task
          Components: shading
    Affects Versions: 2.0.0
            Reporter: Sean Busbey
            Assignee: Sean Busbey
             Fix For: 2.0.0

there are contexts where we want to stay out of our downstream users way wrt dependencies,
but they need more Hadoop classes than we provide. i.e. any downstream client that wants to
use both HBase and HDFS in their application, or any non-MR YARN application.

Now that Hadoop also has shaded client artifacts for Hadoop 3, we're also providing less incremental
benefit by including our own rewritten Hadoop classes to avoid downstream needing to pull
in all of Hadoop's transitive dependencies.

right now those users need to ensure that any jars from the Hadoop project are loaded in the
classpath prior to our shaded client jar. This is brittle and prone to weird debugging trouble.

instead, we should have two artifacts: one that just lists Hadoop as a prerequisite and one
that still includes the rewritten-but-not-relocated Hadoop classes.

We can then use docs to emphasize when each of these is appropriate to use.

This message was sent by Atlassian JIRA

View raw message