[
https://issues.apache.org/jira/browse/HBASE-24018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17062193#comment-17062193
]
Andrew Kyle Purtell commented on HBASE-24018:
---------------------------------------------
bq. what's actually needed here is the ability for a user without admin
privileges to check for the presence or absence of a coprocessor, not the
entire TableDescriptor. This is needed because Phoenix clients have to behave
differently depending on whether the legacy or new indexing coprocessor is
installed, which will greatly change the behavior on the server.
I also think you can just add a Phoenix endpoint API. There could be some
utility in adding an API for listing installed coprocessors, not arguing that,
but aside from this Phoenix case is there a use case for it on deck?
> Coprocessor existence check for READ level privilege
> ----------------------------------------------------
>
> Key: HBASE-24018
> URL: https://issues.apache.org/jira/browse/HBASE-24018
> Project: HBase
> Issue Type: Improvement
> Reporter: Abhishek Singh Chouhan
> Priority: Major
>
> Currently getTableDescriptor requires a user to have Admin or Create
> permissions. A client might need to get table descriptors to act accordingly
> eg. based on an attribute set or a CP loaded. It should not be necessary for
> the client to have create or admin privileges just to read the descriptor,
> execute and/or read permission should be sufficient?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
