hdygxsj commented on code in PR #9035: URL: https://github.com/apache/gravitino/pull/9035#discussion_r2501825915
########## docs/security/access-control.md: ########## @@ -264,6 +265,13 @@ DENY `WRITE_FILESET` won‘t deny the `READ_FILESET` operation if the user has t | CREATE_MODEL_VERSION | Metalake, Catalog, Schema, Model | Create a model version | | USE_MODEL | Metalake, Catalog, Schema, Model | View the metadata of the model and download all the model versions | +### Tag privileges + +| Name | Supports Securable Object | Operation | +|------------|---------------------------|--------------| +| CREATE_TAG | Metalake | Create a tag | +| APPLY_TAG | Metalake, Tag | Apply a tag | Review Comment: > It seems that the tag is only visible to the users who has privileges. This differs from Snowflake's design. In our company's context, consider a shared data warehouse table where multiple users might apply different tags. If everyone can see the tags applied by others—and especially if the company has many employees—it could become quite chaotic. I think I'd prefer to only see the tags that I myself have applied. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
