You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Appy (JIRA)" <ji...@apache.org> on 2017/09/28 01:32:00 UTC

[jira] [Updated] (HBASE-18884) Coprocessor Design Improvements follow up of HBASE-17732

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

Appy updated HBASE-18884:
-------------------------
    Summary: Coprocessor Design Improvements follow up of HBASE-17732  (was: Coprocessor Design Improvements 2 (Follow up of HBASE-17732))

> Coprocessor Design Improvements follow up of HBASE-17732
> --------------------------------------------------------
>
>                 Key: HBASE-18884
>                 URL: https://issues.apache.org/jira/browse/HBASE-18884
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Appy
>            Assignee: Appy
>             Fix For: 2.0.0-alpha-4
>
>
> Creating new jira to track suggestions that came in review (https://reviews.apache.org/r/62141/) but are not blocker and can be done separately.
> Suggestions by [~apurtell]
> -  Change {{Service Coprocessor#getService()}} to {{List<Service> Coprocessor#getServices()}}
> - I think we overstepped by offering [table resource management via this interface|https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/CoprocessorEnvironment.java#L57]. There are a lot of other internal resource types which could/should be managed this way but they are all left up to the implementor. Perhaps we should remove the table ref management and leave it up to them as well.
> ----
> - Checkin the finalized design doc into repo (https://docs.google.com/document/d/1mPkM1CRRvBMZL4dBQzrus8obyvNnHhR5it2yyhiFXTg/edit) (fyi: [~stack])
> - Added example to javadoc of Coprocessor base interface on how to implement one in the new design



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)