[
https://issues.apache.org/jira/browse/PHOENIX-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16266767#comment-16266767
]
Ankit Singhal commented on PHOENIX-4399:
----------------------------------------
bq. When AC find un authorized access, it throws an IOException type. The IOE
is handled differently. We just throw back to client side. So IOE is handled.
Any other type comes, this config gets into action.
>From security perspective, I was expecting, that AC should never be unloaded
>even if for some reason it throws non- IOE exception.(any RunTimeException)
Thanks [~anoopsamjohn], I see Stack raised HBASE-19341 for special exception.
Just committing the patch in 5.x so that team can continue fixing test-cases,
I'll keep this JIRA open to fix the Exception once HBASE-19341 is resolved.
> Remove explicit abort on RegionServerServices
> ---------------------------------------------
>
> Key: PHOENIX-4399
> URL: https://issues.apache.org/jira/browse/PHOENIX-4399
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: Ankit Singhal
> Assignee: Ankit Singhal
> Labels: HBase-2.0
> Attachments: PHOENIX-4399.patch
>
>
> Suggestions from @stack and [~anoop.hbase] from HBASE-18298
> Though regionServerServices are not visible from the environment, we can
> still let CoprocessorHost abort the RS if observer/coprocessor throws
> exception other than IOException and hbase.coprocessor.abortonerror is not
> set to false.
> But how to ensure that ABORT_ON_ERROR is never set to false in case of
> Phoenix. or should we have some special exception in HBase for forcefull
> abort.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
