[
https://issues.apache.org/jira/browse/SENTRY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15107688#comment-15107688
]
Sravya Tirukkovalur commented on SENTRY-1001:
---------------------------------------------
When we have a URI without a scheme is being used in a Hive operation, I do not
think it is definitive that it would be a hdfs location. I guess hive has some
semantics around how it defaults. Would be best to handle them similarly in the
Hive binding hook of Sentry.
> Improve usability of URIs and URI privileges
> ---------------------------------------------
>
> Key: SENTRY-1001
> URL: https://issues.apache.org/jira/browse/SENTRY-1001
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Lenni Kuff
> Assignee: Ryan P
>
> Sentry currently requires users to have their URI privileges exactly match
> what is in the CREATE TABLE statement. For example, the following will not
> work:
> GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table'
> CREATE EXTERNAL TABLE foo LOCATION '/path/to/table'
> To make this more usable, Sentry should automatically handle this case and
> apply whatever the default scheme and authority based on the HDFS configs
> Sentry has been given.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
