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 Kyle Purtell (Jira)" <ji...@apache.org> on 2021/03/09 00:44:00 UTC

[jira] [Updated] (HBASE-25647) ChoreService should be LimitedPrivate(COPROC)

     [ https://issues.apache.org/jira/browse/HBASE-25647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell updated HBASE-25647:
----------------------------------------
    Description: ChoreService is marked Public and is in hbase-common but is not part of our public client API. We aren't providing a library for scheduling chores and such; we are providing a client library for accessing remote HBase service. As part of the server framework, where it could be useful for coprocessors, it makes more sense to expose it as supported for that purpose. I believe this was the intent of marking it Public. However I argue it should be LimitedPrivate(COPROC) instead, which is the appropriate classification for server internal components we want to expose to plug ins.   (was: ChoreService is marked Public but is not part of our client API nor will be. It is a server side class, part of the server framework, and could be useful for coprocessors. I believe this was the intent of marking it Public. However it should be LimitedPrivate(COPROC) for that purpose. )

> ChoreService should be LimitedPrivate(COPROC)
> ---------------------------------------------
>
>                 Key: HBASE-25647
>                 URL: https://issues.apache.org/jira/browse/HBASE-25647
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.4.2
>            Reporter: Andrew Kyle Purtell
>            Priority: Major
>             Fix For: 3.0.0-alpha-1, 2.5.0, 2.4.3
>
>
> ChoreService is marked Public and is in hbase-common but is not part of our public client API. We aren't providing a library for scheduling chores and such; we are providing a client library for accessing remote HBase service. As part of the server framework, where it could be useful for coprocessors, it makes more sense to expose it as supported for that purpose. I believe this was the intent of marking it Public. However I argue it should be LimitedPrivate(COPROC) instead, which is the appropriate classification for server internal components we want to expose to plug ins. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)