Mailing-List: contact dev-help@hawq.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hawq.incubator.apache.org
From: dyozie <git@git.apache.org>
To: dev@hawq.incubator.apache.org
Reply-To: dev@hawq.incubator.apache.org
References: <git-pr-109-incubator-hawq-docs@git.apache.org>
In-Reply-To: <git-pr-109-incubator-hawq-docs@git.apache.org>
Subject: [GitHub] incubator-hawq-docs pull request #109: deferring super-user events discussio...
Content-Type: text/plain
Message-Id: <20170331161553.89D01DFE34@git1-us-west.apache.org>
Date: Fri, 31 Mar 2017 16:15:53 +0000 (UTC)
archived-at: Fri, 31 Mar 2017 16:16:00 -0000

Github user dyozie commented on a diff in the pull request:

    https://github.com/apache/incubator-hawq-docs/pull/109#discussion_r109196703
  
    --- 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 --
    
    Maybe lose the second bullet and edit the final one to say "HAWQ catalog-related built-in functions such as ..."


---
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.
---