About Doris User Permissions
Table 1 lists the permissions supported by the Doris.
Permission |
Permission Introduction |
---|---|
Node_priv |
Node change permission. Add, delete, and bring offline FE, BE, and DBroker nodes. This permission can be granted only to the Global level. |
Admin_priv |
All permissions except NODE_PRIV. |
Grant_priv |
Permission change permission, including granting permissions, revoking permissions, and adding, deleting, and changing users and roles. Users with this permission cannot grant the node_priv permission to other users unless they already have the node_priv permission. |
Select_priv |
Read-only permission on databases and tables. |
Load_priv |
Write permission on databases and tables, including Load, Insert, and Delete. |
Alter_priv |
Permission to modify databases and tables. including renaming databases or tables, adding, deleting, or changing columns, and adding or deleting partitions. |
Create_priv |
Permission to create databases, tables, and views. |
Drop_priv |
Delete permissions on databases, tables, and views. |
Usage_priv |
Permissions to use resources and workload groups. |
Database table permissions are classified into the following four levels based on the permission application scope:
- CATALOG LEVEL: data directory-level permission. The granted permission applies to any database table in the specified catalog.
- DATABASE LEVEL: database-level permission. The granted permissions apply to any table in the specified database.
- TABLE LEVEL: table-level permission. The granted permissions apply to the specified table in the specified database.
- RESOURCE LEVEL: resource-level permission. The granted permission applies to the specified resource.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot