[ 
https://issues.apache.org/jira/browse/HIVE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14055975#comment-14055975
 ] 

Lefty Leverenz commented on HIVE-6846:
--------------------------------------

This adds *hive.security.authorization.sqlstd.confwhitelist* with a description 
in the HiveConf.java comment but not in hive-default.xml.template.

It's documented in the wiki here (please review, I made the assumption that 
it's a comma-separated list):

* [Configuration Properties -- hive.security.authorization.sqlstd.confwhitelist 
| 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-hive.security.authorization.sqlstd.confwhitelist]

with references from two places:

* [SQL Standard Based Hive Authorization -- Restrictions on Hive Commands and 
Statements | 
https://cwiki.apache.org/confluence/display/Hive/SQL+Standard+Based+Hive+Authorization#SQLStandardBasedHiveAuthorization-RestrictionsonHiveCommandsandStatements]
* [Configuration Properties -- Restricted List and Whitelist | 
https://cwiki.apache.org/confluence/display/Hive/Configuration+Properties#ConfigurationProperties-RestrictedListandWhitelist]

I added a comment to HIVE-6586 so the parameter description won't get lost in 
the shuffle when HIVE-6037 changes HiveConf.java.

> allow safe set commands with sql standard authorization
> -------------------------------------------------------
>
>                 Key: HIVE-6846
>                 URL: https://issues.apache.org/jira/browse/HIVE-6846
>             Project: Hive
>          Issue Type: Bug
>          Components: Authorization
>    Affects Versions: 0.13.0
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>             Fix For: 0.13.0
>
>         Attachments: HIVE-6846.1.patch, HIVE-6846.2.patch, HIVE-6846.3.patch
>
>
> HIVE-6827 disables all set commands when SQL standard authorization is turned 
> on, but not all set commands are unsafe. We should allow safe set commands.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to