[
https://issues.apache.org/jira/browse/SENTRY-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378716#comment-15378716
]
Sravya Tirukkovalur commented on SENTRY-1390:
---------------------------------------------
With respect to the impact: I guess my main concern is what if schemas and
authorities of warehouse and fsDefault are different?
For example: warehouse = s3://authority/path and fsDefault =
hdfs://authority/path and if path = hdfs:///path (missing scheme)
Pre 1390 behavior is hdfs://authority/path, post 1390 behavior is
s3://authority/path. This does not seem like a low risk behavior change to me
if this is a fair use case.
I agree that the test is HMS specific, but the fix isnt. So if we are just
doing a test only patch then calling it HMS makes sense.
> 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)
