[ https://issues.apache.org/jira/browse/SENTRY-951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999207#comment-14999207 ]
Sravya Tirukkovalur commented on SENTRY-951: -------------------------------------------- In hive, warehouse directory's path is equivalent to path of the "default" database. For example: If warehouse.dir = /hive, and if we create a table it would be created at /hive/tab1. Where as non default databases are created at /hive/db1.db and so on. As /hive is now a location which corresponds to a hive object (db) and is in prefix path, it should be sentry managed. This should be true for default warehouse.dir = /user/warehouse/hive. Coming to your question [~Ryan P]. Yes, it is quite possible that the /user/hive/warehouse is hive:hive due to the setup and it is not necessarily sentry managed. I would expect so. > move hive warehouse dir to /hive, the dir doesn't have hive:hive as owner. > -------------------------------------------------------------------------- > > Key: SENTRY-951 > URL: https://issues.apache.org/jira/browse/SENTRY-951 > Project: Sentry > Issue Type: Bug > Reporter: Anne Yu > > {noformat} > sudo -u hdfs hdfs dfs -mkdir -p /another > sudo -u hdfs hdfs dfs -getfacl /another > hfds:supergroup > {noformat} > put /another into hive.metastore.warehouse.dir; > add /another into hdfs sentry syncup prefix; > restart hive, sentry, hdfs > {code} > [root@anneyu-538-1 ~]# sudo -u hdfs hdfs dfs -getfacl /another > # file: /another > # owner: hdfs > # group: supergroup > user::rwx > group::r-x > other::r-x > {code} > If create table will get the below errors: > {code} > 0: jdbc:hive2://anneyu-538-4.vpc.cloudera.com> create table test7(s string); > Error: Error while processing statement: FAILED: Execution Error, return code > 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got > exception: org.apache.hadoop.security.AccessControlException Permission > denied: user=hive, access=WRITE, inode="/another":hdfs:supergroup:drwxr-xr-x > {code} -- This message was sent by Atlassian JIRA (v6.3.4#6332)