[
https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16165723#comment-16165723
]
stack commented on HBASE-18601:
-------------------------------
[~tamaas] The findbugs looks legit and the first test I tried failed locally
for me; does it fail for you sir?
On the patch:
The exclusions of old htrace seem like a good idea.
Man, looking at all the null checks reminds me of how the htrace API needs a
bit of work...
But patch seems fine sir. We can do hookup in a follow-on.
> Update Htrace to 4.2
> --------------------
>
> Key: HBASE-18601
> URL: https://issues.apache.org/jira/browse/HBASE-18601
> Project: HBase
> Issue Type: Task
> Affects Versions: 2.0.0, 3.0.0
> Reporter: Tamas Penzes
> Assignee: stack
> Fix For: 2.0.0-alpha-3
>
> Attachments: HBASE-18601.master.001.patch,
> HBASE-18601.master.002.patch
>
>
> HTrace is not perfectly integrated into HBase, the version 3.2.0 is buggy,
> the upgrade to 4.x is not trivial and would take time. It might not worth to
> keep it in this state, so would be better to remove it.
> Of course it doesn't mean tracing would be useless, just that in this form
> the use of HTrace 3.2 might not add any value to the project and fixing it
> would be far too much effort.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
> Based on the decision of the community we keep htrace now and update version
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
