[
https://issues.apache.org/jira/browse/HBASE-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16410511#comment-16410511
]
Mike Drob commented on HBASE-19158:
-----------------------------------
I'm not going to point out things that are missing because I'll assume you just
haven't gotten to that issue yet.
{code}
+Note that this artifact exposes some classes in the org.apache.hadoop package
space (e.g. o.a.h.configuration.Configuration) so that we can maintain source
compatibility with our public API. Those classes are included so that they can
be altered to use the same relocated third party dependencies as the rest of
the HBase client code. In the event that you need to *also* use Hadoop in your
code, you should ensure all Hadoop related jars precede the HBase client jar in
your classpath.
{code}
This is repeated for client and shaded-mapreduce. Is it accurate for the mr
story? They necessarily must be using hadoop jars, right, for things like
Job/Mapper/etc.
{code}
Downstream client users who do not follow the guidance in
[[2.0.shaded.client.preferred]]
{code}
I think this is the wrong heading link
> Ref guide needs upgrade update
> ------------------------------
>
> Key: HBASE-19158
> URL: https://issues.apache.org/jira/browse/HBASE-19158
> Project: HBase
> Issue Type: Task
> Components: documentation
> Affects Versions: 2.0.0-beta-1
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: HBASE-19158.0.patch
>
>
> Our ref guide has lots of references in the upgrade section to obsolete
> versions and no references to the 2.0.0-* releases. We should correct this
> for beta-1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
