You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Alex Rodoni (JIRA)" <ji...@apache.org> on 2018/03/21 23:19:00 UTC

[jira] [Resolved] (IMPALA-6654) [DOCS] Kudu/Sentry docs are out of date

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

Alex Rodoni resolved IMPALA-6654.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 2.12.0

> [DOCS] Kudu/Sentry docs are out of date
> ---------------------------------------
>
>                 Key: IMPALA-6654
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6654
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Docs
>    Affects Versions: Impala 2.11.0
>            Reporter: Thomas Tauber-Marshall
>            Assignee: Alex Rodoni
>            Priority: Critical
>              Labels: docs
>             Fix For: Impala 2.12.0
>
>
> The documentation of Impala's support for Sentry authorization on Kudu tables, available here:
> http://impala.apache.org/docs/build/html/topics/impala_kudu.html
> is out of date. It should be updated to include the changes made in IMPALA-5489. In particular:
> - Access is no longer "all or nothing" - we support column-level permissions
> - Permissions do not apply "to all SQL operations" - we support SELECT- and INSERT-specific permissions. DELETE/UPDATE/UPSERT still require ALL
> We should also document that "all on server" is required to specify "kudu.master_addresses" in a CREATE, even for managed tables, in addition to be required to CREATE any external table.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)