[ https://issues.apache.org/jira/browse/HIVE-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993106#comment-13993106 ]
Thejas M Nair commented on HIVE-6846: ------------------------------------- That failure does not indicate a product problem. In fact there is no reason to set local scratch dirs to 777 . That change was part of HIVE-5486. The idea is that in HS2, with doAs enabled, the files/subdirs under scratch dir happens as the end user. But in case of local file system, this is not true, all file creation happens as the HS2 server user. There are some changes that Vaibhav and Vikram have been working on to create the base scratch dir as the actual user running the query. That will help address this issue. The test issue is already not there in trunk. I don't think this should block 0.13.1 release. > 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)