[SENTRY-1001] Improve usability of URIs and URI privileges

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6.0
• Fix Version/s: 1.8.0
• Component/s: URI
• Assignee: Hao Hao
• Reporter: Lenni Kuff
• Created: 07/Jan/16 18:59
• Updated: 07/Jul/16 23:57
• Resolved: 26/Apr/16 04:16

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.

Issue Links

• is duplicated by: SENTRY-722 Grant on URI should validate the required resource string format
• is duplicated by: SENTRY-807 Grant on URI should prepend namenode prefix
• is related to: SENTRY-1002 PathsUpdate.parsePath(path) will throw an NPE when parsing relative paths
• relates to: SENTRY-1153 Ensure AccessURI work with S3
• relates to: SENTRY-1390 Add test cases to ensure usability of URI privileges for HMS binding

Sub-Tasks

• Improve usability of URI privileges when granting URIs: Resolved
• Support of URI privilege without scheme should be configurable: Resolved