[
https://issues.apache.org/jira/browse/HBASE-22874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910005#comment-16910005
]
Andrew Purtell commented on HBASE-22874:
----------------------------------------
Something else which could work is refactor of Canary to public annotated
interface with move of implementation to an impl class. I think this can be
done later? If canary ‘interface’ is done as an abstract class the result
should be source and binary compatible. Anyway I would approve a patch that
does that. Could be LP(tools) if someone can explain how that differs from
public. Does that mean we can expect arbitrary breaks? No thanks. Is there
something onerous about canary as public interface? I don’t see it but could be
convinced.
> 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)
