[FEATURE] Support for more granular permissions.
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 298
Description
### Describe the feature
Currently, the permission granularity supported by Gravitino is relatively coarse. We hope that Gravitino can support more granular permissions.
### Motivation
In order to meet the customer's needs for refined permission control.
### Describe the solution
| user | add user, remove user | MANAGE\_USERS |
| :---- | :---- | :---- |
| group | add group, remove group | MANAGE\_GROUPS |
| catalog | ALL | \- |
| catalog | alter catalog | \- |
| catalog | drop catalog | \- |
| catalog | create schema | CREATE\_SCHEMA |
| catalog | grant | \- |
| schema | ALL | \- |
| schema | alter schema | \- |
| schema | drop | \- |
| schema | create table | CREATE\_TABLE |
| schema | grant | \- |
| table | …… | …… |
| topic | …… | …… |
| fileset | …… | …… |
### Additional context
_No response_
Contributor guide
Research direction
The issue names no files, tests, or entry points to inspect. Start by reviewing the existing permission model and its supported catalog, schema, table, topic, and fileset operations; done means agreeing on and implementing a complete granular permission matrix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authorization
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100