[
https://issues.apache.org/jira/browse/HBASE-12938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14522416#comment-14522416
]
Andrew Purtell commented on HBASE-12938:
----------------------------------------
The package name change alone means the result is going to be incompatible,
both for code and Maven. I think we need to bite the bullet and move to a
recent org.apache.htrace release, mark it as an incompatible change, and
explain the ramifications in a release note. Tracing during rolling upgrade
won't work.
Let me work up a simple patch for this.
Alternatively, we could rip out all HTrace code in 0.98 referencing the dead
com.cloudera.htrace versions.
I would prefer we acknowledge HTrace's usefulness, and status as an incubating
project, and roll with it.
> Upgrade HTrace to a recent supportable incubating version
> ---------------------------------------------------------
>
> Key: HBASE-12938
> URL: https://issues.apache.org/jira/browse/HBASE-12938
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Fix For: 0.98.13
>
>
> In 0.98 we have an old htrace (still using the org.cloudera.htrace package)
> and since the introduction of htrace code, htrace itself first moved to
> org.htrace, then became an incubating project. I filed this as a bug because
> the HTrace version we reference in 0.98 is of little to no use going forward.
> Unfortunately we must make a disruptive change, although it looks to be
> mostly fixing up imports, we expose no HTrace classes to HBase configuration,
> and where we extend HTrace classes in our code, those HBase classes are in
> hbase-server and not tagged for public consumption.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
