database/doris
2
0
Fork 0
Code Issues Pull Requests Actions 3 Packages Projects Releases Wiki Activity
Files
4ccaa0dfc5a95c19f3e4618f4e2fa7df8b392ec9
doris/docs/en/sql-manual/sql-reference/Account-Management-Statements/GRANT.md
Mingyu Chen 74a482ca7f [fix] fix docs build bug (#9293) 
After this PR #9272, the `docs/build_help_zip.sh` will run failed.
This PR fix this issue.
But the help module still has some parse problem, I will fix it in next PR.

This CL mainly changes:
1. fix `docs/build_help_zip.sh` error
2. remove `sql-reference-v2` to `sql-reference`
3. modify build extension github action to run `docs/build_help_zip.sh`
2022-04-28 22:19:04 +08:00

4.2 KiB
Raw Blame History

title, language
title language
GRANT en

GRANT

Name

GRANT

Description

The GRANT command is used to grant the specified user or role specified permissions

GRANT privilege_list ON db_name[.tbl_name] TO user_identity [ROLE role_name]

GRANT privilege_list ON RESOURCE resource_name TO user_identity [ROLE role_name]

privilege_list is a list of privileges to be granted, separated by commas. Currently Doris supports the following permissions:

NODE_PRIV: Cluster node operation permissions, including node online and offline operations. Only the root user has this permission and cannot be granted to other users.
ADMIN_PRIV: All privileges except NODE_PRIV.
GRANT_PRIV: Privilege for operation privileges. Including creating and deleting users, roles, authorization and revocation, setting passwords, etc.
SELECT_PRIV: read permission on the specified library or table
LOAD_PRIV: Import privileges on the specified library or table
ALTER_PRIV: Schema change permission for the specified library or table
CREATE_PRIV: Create permission on the specified library or table
DROP_PRIV: drop privilege on the specified library or table
USAGE_PRIV: access to the specified resource

ALL and READ_WRITE in legacy permissions will be converted to: SELECT_PRIV,LOAD_PRIV,ALTER_PRIV,CREATE_PRIV,DROP_PRIV;
READ_ONLY is converted to SELECT_PRIV.

Permission classification:

1. Node Privilege: NODE_PRIV
2. Library table permissions: SELECT_PRIV, LOAD_PRIV, ALTER_PRIV, CREATE_PRIV, DROP_PRIV
3. Resource permission: USAGE_PRIV

db_name[.tbl_name] supports the following three forms:

1. *.* permissions can be applied to all libraries and all tables in them
2. db.* permissions can be applied to all tables under the specified library
3. The db.tbl permission can be applied to the specified table under the specified library

The library or table specified here can be a library and table that does not exist.

resource_name supports the following two forms:

1. * Permissions apply to all resources
2. The resource permission applies to the specified resource

The resource specified here can be a non-existing resource.

user_identity:

The user_identity syntax here is the same as CREATE USER. And must be a user_identity created with CREATE USER. The host in user_identity can be a domain name. If it is a domain name, the effective time of the authority may be delayed by about 1 minute.

You can also assign permissions to the specified ROLE, if the specified ROLE does not exist, it will be created automatically.

Example

  1. Grant permissions to all libraries and tables to the user

    GRANT SELECT_PRIV ON *.* TO 'jack'@'%';

  2. Grant permissions to the specified library table to the user

    GRANT SELECT_PRIV,ALTER_PRIV,LOAD_PRIV ON db1.tbl1 TO 'jack'@'192.8.%';

  3. Grant permissions to the specified library table to the role

    GRANT LOAD_PRIV ON db1.* TO ROLE 'my_role';

  4. Grant access to all resources to users

    GRANT USAGE_PRIV ON RESOURCE * TO 'jack'@'%';

  5. Grant the user permission to use the specified resource

    GRANT USAGE_PRIV ON RESOURCE 'spark_resource' TO 'jack'@'%';

  6. Grant access to specified resources to roles

    GRANT USAGE_PRIV ON RESOURCE 'spark_resource' TO ROLE 'my_role';

Keywords

GRANT

Best Practice