phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karan Mehta (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-4528) PhoenixAccessController checks permissions only at table level when creating views
Date Sun, 14 Jan 2018 01:21:02 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karan Mehta updated PHOENIX-4528:
---------------------------------
    Attachment: PHOENIX-4528.001.patch

Attaching the patch for QA run.
Please review the patch [~ankit.singhal] or [~twdsilva@gmail.com] on the Github PR.

> PhoenixAccessController checks permissions only at table level when creating views
> ----------------------------------------------------------------------------------
>
>                 Key: PHOENIX-4528
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4528
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Karan Mehta
>         Attachments: PHOENIX-4528.001.patch, PHOENIX-4528.repro-test.diff
>
>
> The {{PhoenixAccessController#preCreateTable()}} method is invoked everytime a user wants
to create a view on a base table. The {{requireAccess()}} method takes in tableName as the
parameter and checks for user permissions only at that table level. The correct approach is
to also check permissions at namespace level, since it is at a larger scope than per table
level.
> For example, if the table name is {{TEST_SCHEMA.TEST_TABLE}}, it will created as {{TEST_SCHEMA:TEST_TABLE}}
HBase table is namespace mapping is enabled. View creation on this table would fail if permissions
are granted to just {{TEST_SCHEMA}} and not on {{TEST_TABLE}}. It works correctly if same
permissions are granted at table level too.
> FYI. [~ankit.singhal] [~twdsilva@gmail.com]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message