[
https://issues.apache.org/jira/browse/HBASE-6899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466096#comment-13466096
]
Andrew Purtell commented on HBASE-6899:
---------------------------------------
On https://reviews.apache.org/r/7242/ there is related discussion about the
semantics of the global configuration hbase.coprocessor.abortonerror, that it
is more appropriately configured per CP. Gary Helmling writes:
{quote}
Fair enough, I can see load failure as a distinct case with it's own semantics.
The original thinking (at least mine) around abortonerror was that it would be
useful to fail-fast during development for debugging purposes. I wasn't
thinking as much about correctness cases where you might want to use it. From
that perspective, it does seem more useful as a per-coprocessor configuration,
though, without the ability to set configuration for system coprocessors, I
don't think we can remove the global config option. Maybe we should open a
separate issue to provide per-system coprocessor configurations somehow.
For abortonerror specifically, another option is to add a method hook to the
Coprocessor interface -- shouldAbortOnError() -- to let the CP implementation
tell you. This would allow system CPs to be included, though it's less
flexible than the per-CP config option. So ultimately it's probably better to
allow per-system CP configs.
{quote}
> [Coprocessors] Add system coprocessor configuration directives
> --------------------------------------------------------------
>
> Key: HBASE-6899
> URL: https://issues.apache.org/jira/browse/HBASE-6899
> Project: HBase
> Issue Type: Improvement
> Components: Coprocessors
> Affects Versions: 0.94.1, 0.96.0
> Reporter: Andrew Purtell
>
> Users can supply per-CP configuration for table coprocessors by way of the
> table CP spec in HTableDescriptor. We have no similar facility for system
> coprocessors (those installed on all regions via Configuration). We should
> add support to set per-CP configuration for system CPs also via Configuration.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
