You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2019/08/18 16:35:00 UTC

[jira] [Comment Edited] (HBASE-22874) Canary should not be IA.Public

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

Andrew Purtell edited comment on HBASE-22874 at 8/18/19 4:34 PM:
-----------------------------------------------------------------

We need an embedding of Canary that is a Public API. 

We embed the canary in our monitoring tool suite. We use code to integrate it instead of log scraping which is brittle and neither scalable or responsive (depends on how you manage logs. We aggregate to Splunk, which has limits.)

I would be interested in a proposal that can achieve our needs 


was (Author: apurtell):
We need an embedding of Canary that is a Public API. 

We embed the canary in our monitoring tool suite. We use code to integrate it instead of log scraping which is brittle and neither scalable or responsive (depends on how you manage logs. We aggregate to Splunk, which has limits.)

I would be interested in a proposal that can achieve our needs but otherwise am -1 for reverting the annotation change we got committed through legit process. 

> Canary should not be IA.Public
> ------------------------------
>
>                 Key: HBASE-22874
>                 URL: https://issues.apache.org/jira/browse/HBASE-22874
>             Project: HBase
>          Issue Type: Bug
>          Components: canary
>            Reporter: Duo Zhang
>            Priority: Blocker
>             Fix For: 3.0.0, 2.3.0, 2.0.6, 2.2.1, 2.1.6
>
>
> It can be marked as IA.LimitedPrivate(TOOLS).



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