hawq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lisakowen <...@git.apache.org>
Subject [GitHub] incubator-hawq-docs pull request #109: deferring super-user events discussio...
Date Fri, 31 Mar 2017 01:42:00 GMT
Github user lisakowen commented on a diff in the pull request:

    --- Diff: markdown/ranger/ranger-policy-creation.html.md.erb ---
    @@ -60,6 +60,8 @@ HAWQ *always* employs its native authorization for operations on its
catalog. HA
     - `CREATE`, `DROP`, or `ALTER` commands for resource queues
     - `CREATE ROLE`, `DROP ROLE`, `SET ROLE`, `createuser`, `dropuser`
     - `CREATE TABLESPACE`, `DROP TABLESPACE` (Ranger does manage authorization for creating
tables and indexes _within_ an existing tablespace.)
    +- Built-in functions such as pg\_logdir\_ls, pg\_ls\_dir, pg\_read\_file, pg\_reload\_conf,
pg\_rotate\_logfile, pg\_signal\_backend, pg\_start\_backup,  pg\_stat\_file, pg\_stat\_get\_activity,
pg\_stat\_get\_backend\_activity\_start, pg\_stat\_get\_backend\_activity, pg\_stat\_get\_backend\_client\_addr,
pg\_stat\_get\_backend\_client\_port, pg\_stat\_get\_backend\_start, pg\_stat\_get\_backend\_waiting,
pg\_stop\_backup, pg\_switch\_xlog, and pg\_stat\_reset.
    --- End diff --
    the second bullet was a catch-all for catalog functions.  i should we remove this bullet,
or keep it in to cover non-listed catalog functions?   (i am not familiar with all of the
catalog functions. )
    looks good.

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message