[
https://issues.apache.org/jira/browse/HBASE-22823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911734#comment-16911734
]
Hudson commented on HBASE-22823:
--------------------------------
SUCCESS: Integrated in Jenkins build HBase-1.3-IT #620 (See
[https://builds.apache.org/job/HBase-1.3-IT/620/])
Revert "HBASE-22823 Mark Canary as Public/Evolving" (apurtell: rev
3351124124485bc832873bdeafee698018d4a2eb)
* (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
> 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
(v8.3.2#803003)
