Description
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.
Attachments
Issue Links
- is duplicated by
-
SENTRY-722 Grant on URI should validate the required resource string format
- Resolved
-
SENTRY-807 Grant on URI should prepend namenode prefix
- Resolved
- is related to
-
SENTRY-1002 PathsUpdate.parsePath(path) will throw an NPE when parsing relative paths
- Resolved
- relates to
-
SENTRY-1153 Ensure AccessURI work with S3
- Resolved
-
SENTRY-1390 Add test cases to ensure usability of URI privileges for HMS binding
- Resolved
1.
|
Improve usability of URI privileges when granting URIs | Resolved | Hao Hao | |
2.
|
Support of URI privilege without scheme should be configurable | Resolved | Unassigned |