This is an automated email from the ASF dual-hosted git repository.
roryqi pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/main by this push:
new b53d67383e [MINOR] docs: supplement missing request path description
for set owner API (#10736)
b53d67383e is described below
commit b53d67383e70653a967bf0327faec2f10bacda2d
Author: jarred0214 <[email protected]>
AuthorDate: Tue Apr 14 10:39:58 2026 +0800
[MINOR] docs: supplement missing request path description for set owner API
(#10736)
### What changes were proposed in this pull request?
Replaced hardcoded values (e.g., test, role1) with standard placeholder
variables (e.g., ${metalake}, ${role}) in the permission API curl
examples within the documentation.
### Why are the changes needed?
The existing documentation examples used hardcoded values like test and
role1 as path parameters, which could mislead users into thinking these
are required or default values rather than user-defined inputs. Using
consistent placeholder variables aligns with the documentation style
used elsewhere in the project.
### Does this PR introduce _any_ user-facing change?
No. This is a documentation-only change. No APIs, property keys, or
runtime behaviors are affected.
### How was this patch tested?
No code changes were made. The fix is documentation only and was
verified by manual review of the updated curl examples.
Co-authored-by: jarred0214 <[email protected]>
---
docs/security/access-control.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/docs/security/access-control.md b/docs/security/access-control.md
index bed791f403..9d84757049 100644
--- a/docs/security/access-control.md
+++ b/docs/security/access-control.md
@@ -955,11 +955,11 @@ curl -X PUT -H "Accept:
application/vnd.gravitino.v1+json" \
```java
GravitinoClient client = ...
-// Grant the privilege allowing `SELEC_TABLE` for the `schema` to `role1`
+// Grant the privilege allowing `SELECT_TABLE` for the `schema` to `role1`
MetadataObject schema = ...
Role role = client.grantPrivilegesToRole("role1", schema,
Lists.newArrayList(Privileges.SelectTable.allow()));
-// Grant the privilege allowing `SELEC_TABLE` for the `table` to `role1`
+// Grant the privilege allowing `SELECT_TABLE` for the `table` to `role1`
MetadataObject table = ...
Role role = client.grantPrivilegesToRole("role1", table,
Lists.newArrayList(Privileges.SelectTable.allow()));
```
@@ -1191,6 +1191,8 @@ Owner owner = client.getOwner(table);
You can set the owner of a metadata object.
+The request path for REST API is
`/api/metalakes/{metalake}/owners/{metadataObjectType}/{metadataObjectName}`.
+
<Tabs groupId='language' queryString>
<TabItem value="shell" label="Shell">
