You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Tamas Penzes (JIRA)" <ji...@apache.org> on 2017/09/13 17:47:01 UTC

[jira] [Comment Edited] (HBASE-18601) Update Htrace to 4.2

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

Tamas Penzes edited comment on HBASE-18601 at 9/13/17 5:46 PM:
---------------------------------------------------------------

after the agreement to not remove htrace I made a new patch to update it to 4.2.0

updated title and description of ticket


was (Author: tamaas):
after the agreement to not remove htrace I made a new patch to update it to 4.2.0

updated title and description

> 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: Tamas Penzes
>             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.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)