[ https://issues.apache.org/jira/browse/HBASE-23710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Geoffrey Jacoby updated HBASE-23710: ------------------------------------ Attachment: HBASE-23710.v1.branch-1.patch > Priority configuration for system coprocessors > ---------------------------------------------- > > Key: HBASE-23710 > URL: https://issues.apache.org/jira/browse/HBASE-23710 > Project: HBase > Issue Type: New Feature > Components: Coprocessors > Reporter: Geoffrey Jacoby > Assignee: Geoffrey Jacoby > Priority: Major > Attachments: HBASE-23710-master.v01.patch, > HBASE-23710.v1.branch-1.patch > > > Currenty HBase allows operators to set system region coprocessors via > hbase-site.xml to be loaded on each table in a cluster (or alternately, all > tables but system tables). HBase assumes that the first loaded system > coprocessor gets the first, or SYSTEM priority, with each subsequent system > coproc getting incremented by 1. As a reminder, in HBase _lower_ priorities > go first. > It can be useful for an operator to be able to define a coprocessor on each > table that needs a different priority. For example, an operator might want a > coproc to load on each table _last_, so that it can enforce some system > invariant and know that no other coproc will interfere with it. > I propose adding optional priority config to the hbase-site.xml > configuration, separated from each coproc class in the comma-separated list > by a special character (perhaps a pipe, such as table coprocs use) that's not > used in class names. > The region coprocessor host will parse the priority if present and use it > when instantiating the coproc. -- This message was sent by Atlassian Jira (v8.3.4#803005)