Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Follow-on from PHOENIX-3652:
The fix provided in PHOENIX-3652 addressed the default situation where users would need ADMIN on the default HBase namespace. However, when phoenix.schema.isNamespaceMappingEnabled=true and Phoenix creates its system tables in the SYSTEM HBase namespace, unprivileged users (those lacking ADMIN on SYSTEM) still cannot connect to Phoenix.
The root-cause is essentially the same: the code tries to fetch the NamespaceDescriptor for the SYSTEM namespace which requires the ADMIN permission.
Attachments
Attachments
Issue Links
- is duplicated by
-
PHOENIX-2717 Unable to login if no "create" permission in HBase
- Resolved
- is related to
-
PHOENIX-3652 Users who do not have global access to hbase cluster can't connect to phoenix
- Resolved
- relates to
-
PHOENIX-3833 Create system schema fails on namespace-mapping table for unprivileged user.
- Resolved