hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18601) Remove Htrace 3.2
Date Wed, 16 Aug 2017 18:01:00 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129168#comment-16129168

Andrew Purtell commented on HBASE-18601:

There is a discussion underway about moving htrace to the attic. See https://lists.apache.org/thread.html/ff87eb11bbfc3ca27a83c0ab377459767a46175447f763b1bf052987@%3Cdev.htrace.apache.org%3E

If this happens I withdraw my objection. The remaining question would then be only which branches
the patch should be applied to.

> Remove Htrace 3.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: Andrew Purtell
>             Fix For: 2.0.0
>         Attachments: HBASE-18601.master.001.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.

This message was sent by Atlassian JIRA

View raw message