hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-19123) Purge 'complete' support from Coprocesor Observers
Date Tue, 05 Dec 2017 06:33:00 GMT

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

stack updated HBASE-19123:
    Attachment: HBASE-19123.master.005.patch

> Purge 'complete' support from Coprocesor Observers
> --------------------------------------------------
>                 Key: HBASE-19123
>                 URL: https://issues.apache.org/jira/browse/HBASE-19123
>             Project: HBase
>          Issue Type: Task
>          Components: Coprocessors
>            Reporter: stack
>            Assignee: stack
>             Fix For: 2.0.0-beta-1
>         Attachments: HBASE-19123.master.001.patch, HBASE-19123.master.002.patch, HBASE-19123.master.003.patch,
HBASE-19123.master.004.patch, HBASE-19123.master.005.patch
> Up on dev list under '[DISCUSSION] Removing the bypass semantic from the Coprocessor
APIs', we are discussing purge of 'complete'. Unless objection, lets purge for beta-1.
> [~andrew.purtell@gmail.com] says the following up on the dev list:
> It would simplify the theory of operation for coprocessors if we can assume either the
entire chain will complete or one of the coprocessors in the chain will throw an exception
that not only terminates processing of the rest of the chain but also the operation in progress.
> Security coprocessors interrupt processing by throwing an exception, which is meant to
propagate all the way back to the user.
> I think it's more than fair to ask the same question about 'complete' as we did about
'bypass': Does anyone use it? Is it needed?

This message was sent by Atlassian JIRA

View raw message