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.