[
https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378682#comment-15378682
]
Hao Hao commented on SENTRY-1390:
---------------------------------
[~sravya] I think the jira is indeed related to HMS binding, the test case is
related to HMSendToend, however it turns out to be a more test case Jira
because of the work in Sentry-1311. I can change the description to test cases
for HMS binding? And regards to the impact, the changes is to default to
metastoredir authority if there is no authority in URI, I do not expect it to
cause any regression. e.g. hdfs:///path will become hdfs://authority/path.
since it apply with the current logic of defaulting to metastoredir. Please let
me know if you think otherwise. Thanks!
> Enabling usability of URI privileges for HMS binding
> ----------------------------------------------------
>
> Key: SENTRY-1390
> URL: https://issues.apache.org/jira/browse/SENTRY-1390
> Project: Sentry
> Issue Type: Task
> Components: URI
> Affects Versions: 1.8.0
> Reporter: Hao Hao
> Assignee: Hao Hao
> Attachments: SENTRY-1390.0.patch, SENTRY-1390.1.patch,
> SENTRY-1390.2.patch
>
>
> Enabling usability of URI privileges for HMS write protection, such that URI
> with no scheme or authority can be handled. e.g
> * GRANT ALL ON URI 'hdfs://namenode:XXX/path/to/table'
> * CREATE EXTERNAL TABLE foo LOCATION '/path/to/table'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
