Hudson commented on HBASE-22823:

Results for branch branch-1.4
        [build #961 on 
(x) *{color:red}-1 overall{color}*
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general 

(x) {color:red}-1 jdk7 checks{color}
-- For more information [see jdk7 

(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) 

(/) {color:green}+1 source release artifact{color}
-- See build output for details.

> 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

Reply via email to