[
https://issues.apache.org/jira/browse/HBASE-17884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16827183#comment-16827183
]
Andrew Purtell commented on HBASE-17884:
----------------------------------------
Hmm.
I pushed a revert to branch-1.4 and updated the fixversions. I think this
resolves the problem on our side.
In general, we are allowed to break CP APIs at minor releases unless they are
specially marked as Stable.
That said, nobody wants to break Phoenix on a whim. However in this case I
think nobody should be extending ObserverContext, this seems like an internal
implementation detail. They can be referenced, of course, we are going to be
careful to preserve interface compatibility for getters, setters, and other
methods, but constructors, not so much, as we expect HBase is the only one
constructing these, for the CP upcalls. This could be an ongoing source of
fragility.
> Backport HBASE-16217 to branch-1
> --------------------------------
>
> Key: HBASE-17884
> URL: https://issues.apache.org/jira/browse/HBASE-17884
> Project: HBase
> Issue Type: Sub-task
> Components: Coprocessors, security
> Reporter: Gary Helmling
> Assignee: Gary Helmling
> Priority: Major
> Fix For: 1.5.0, 1.4.10
>
> Attachments: HBASE-17884-branch-1.patch, HBASE-17884-branch-1.patch,
> HBASE-17884.branch-1.001.patch
>
>
> The change to add calling user to ObserverContext in HBASE-16217 should also
> be applied to branch-1 to avoid use of UserGroupInformation.doAs() for access
> control checks.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
