GRANT

Name

GRANT

Description

The GRANT command has the following functions:

  1. Grant the specified permissions to a user or role.
  2. Grant the specified role to a user.

Note that.

“Grant specified roles to user” is supported in versions 2.0 and later

  1. GRANT privilege_list ON priv_level TO user_identity [ROLE role_name]
  3. GRANT privilege_list ON RESOURCE resource_name TO user_identity [ROLE role_name]
  5. GRANT role_list TO user_identity

SinceVersion devGRANT privilege_list ON WORKLOAD GROUP workload_group_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:

  1. NODE_PRIV: Cluster node operation permissions, including node online and offline operations. User who has NODE_PRIV and GRANT_PRIV permission, can grant NODE_PRIV to other users.
  2. ADMIN_PRIV: All privileges except NODE_PRIV.
  3. GRANT_PRIV: Privilege for operation privileges. Including creating and deleting users, roles, authorization and revocation, setting passwords, etc.
  4. SELECT_PRIV: read permission on the specified database or table
  5. LOAD_PRIV: Import privileges on the specified database or table
  6. ALTER_PRIV: Schema change permission for the specified database or table
  7. CREATE_PRIV: Create permission on the specified database or table
  8. DROP_PRIV: drop privilege on the specified database or table
  9. USAGE_PRIV: access to the specified resource
  10. SHOW_VIEW_PRIV: View permission to `view` creation statements (starting from version 2.0.3, 'SELECT_PRIV' and 'LOAD_PRIV' permissions cannot be 'SHOW CREATE TABLE view_name', has one of `CREATE_PRIV`，`ALTER_PRIV`，`DROP_PRIV`，`SHOW_VIEW_PRIV` can `SHOW CREATE TABLE view_name`) 
  12. ALL and READ_WRITE in legacy permissions will be converted to: SELECT_PRIV,LOAD_PRIV,ALTER_PRIV,CREATE_PRIV,DROP_PRIV;
  13. READ_ONLY is converted to SELECT_PRIV.

Permission classification:

  1. 1. Node Privilege: NODE_PRIV
  2. 2. database table permissions: SELECT_PRIV, LOAD_PRIV, ALTER_PRIV, CREATE_PRIV, DROP_PRIV
  3. 3. Resource  <version since="dev" type="inline" >and workload groups</version> Privilege: USAGE_PRIV

Priv_level supports the following four forms:

  1. 1. *.*.* permissions can be applied to all catalogs, all databases and all tables in them
  2. 2. catalog_name.*.* permissions can be applied to all databases and all tables in them
  3. 3. catalog_name.db.* permissions can be applied to all tables under the specified database
  4. 4. catalog_name.db.tbl permission can be applied to the specified table under the specified database
  6. The catalog or database, table specified here may be not exist.

resource_name supports the following two forms:

  1. 1. * Permissions apply to all resources
  2. 2. The resource permission applies to the specified resource
  4. The resource specified here can be a non-existing resource. In addition, please distinguish the resources here from external tables, and use catalog as an alternative if you use external tables.

workloadgroup_name specifies the workload group name and supports % and `match characters,%can match any string and_` matches any single character.

user_identity:

  1. 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.
  3. You can also assign permissions to the specified ROLE, if the specified ROLE does not exist, it will be created automatically.

role_list is the list of roles to be assigned, separated by commas,the specified role must exist.

Example

  1. Grant permissions to all catalog and databases and tables to the user

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

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

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

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

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

  4. Grant access to all resources to users

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

  5. Grant the user permission to use the specified resource

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

  6. Grant access to specified resources to roles

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

SinceVersion 2.0.0

  1. Grant the specified role to a user

    1. GRANT 'role1','role2' TO 'jack'@'%';

SinceVersion dev

  1. Grant the specified workload group ‘g1’ to user jack

    1. GRANT USAGE_PRIV ON WORKLOAD GROUP 'g1' TO 'jack'@'%'.

  2. match all workload groups granted to user jack

    1. GRANT USAGE_PRIV ON WORKLOAD GROUP '%' TO 'jack'@'%'.

  3. grant the workload group ‘g1’ to the role my_role

    1. GRANT USAGE_PRIV ON WORKLOAD GROUP 'g1' TO ROLE 'my_role'.

  4. Allow jack to view the creation statement of view1 under db1

    1. GRANT SHOW_VIEW_PRIV ON db1.view1 TO 'jack'@'%';

Keywords

  1. GRANT

Best Practice