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

Hudson commented on HBASE-22823:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #619 (See 
[https://builds.apache.org/job/HBase-1.3-IT/619/])
HBASE-22823 Mark Canary as Public/Evolving (xucang: rev 
f8695bbe098f778b7d6841e02cb47e00849eae4f)
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/tool/Canary.java


> Mark Canary as Public/Evolving
> ------------------------------
>
>                 Key: HBASE-22823
>                 URL: https://issues.apache.org/jira/browse/HBASE-22823
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Andrew Purtell
>            Assignee: Caroline
>            Priority: Minor
>             Fix For: 3.0.0, 1.5.0, 2.2.1, 2.1.6, 1.3.6, 1.4.11
>
>         Attachments: HBASE-22823.branch-1.000.patch, 
> HBASE-22823.branch-2.000.patch, HBASE-22823.master.000.patch
>
>
> Canary is marked as a Private class. Its interfaces could change at any time. 
> Should we change the annotation on Canary to Public/Evolving? Or add 
> annotations on some of these subtypes? I think it depends on how we think 
> Canary results should be consumed.
> In our production we find that scraping logs and parsing them is brittle and 
> not scalable. Although the scalability issue is more to do with the totality 
> of logs from a Hadoopish stack, if you run HBase then you have this problem, 
> and you wouldn't be using the canary if you didn't run HBase. We have a tool 
> that embeds the Canary and calls various methods and takes actions without 
> needing a round trip to the logs and whatever aggregates them.
> I propose we promote Canary to Public/Evolving. 



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to