IMPALA-13271: Correct the documentation with respect to granting privileges on URI

Currently, when an administrator grants a privilege on a URI to
a grantee via impala-shell, the created policy in Ranger's policy 
repository is non-recursive.

That is, the policy does not apply for any directory under the URI.
This patch corrects this in the documentation.

Change-Id: Ife9f07294fb0f0b24acb1c8d0199c64ec7d73e9a
Reviewed-on: http://gerrit.cloudera.org:8080/21633
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Reviewed-by: Fang-Yu Rao <fangyu.rao@cloudera.com>
This commit is contained in:
m-sanjana19
2024-08-02 12:03:47 +05:30
committed by Fang-Yu Rao
parent 0918147e69
commit 7d72a0c17d

View File

@@ -255,14 +255,11 @@ under the License.
<conbody>
<p>
URIs represent the file paths you specify as part of statements such as <codeph>CREATE
EXTERNAL TABLE</codeph> and <codeph>LOAD DATA</codeph>. Typically, you specify what
look like UNIX paths, but these locations can also be prefixed with
<codeph>hdfs://</codeph> to make clear that they are really URIs. To set privileges
for a URI, specify the name of a directory, and the privilege applies to all the files
in that directory and any directories underneath it.
</p>
<p> URIs represent the file paths you specify as part of statements such as <codeph>CREATE
EXTERNAL TABLE</codeph> and <codeph>LOAD DATA</codeph>. Typically, you specify what look
like UNIX paths, but these locations can also be prefixed with <codeph>hdfs://</codeph> to
make clear that they are really URIs. To set privileges for a URI, specify the name of a
directory, and the privilege applies to all the files in that directory. </p>
<p>
URIs must start with <codeph>hdfs://</codeph>, <codeph>s3a://</codeph>,