You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gravitino unified authorization will use multiple authorization plugins for different catalogs. For relational catalogs, they usually supports GRANT/REVOKE SQL to authorize.
The plugin will support use SQL to authorize. In Gravitino, we have three kinds of relational catalog.
Hive catalog: a big data typical data catalog. Maybe we should use Hive client to execute the SQL.
Jdbc catalogs: MySQL, PostSQL and etc , they use Jdbc library to execute SQL.
Lakehouse catalogs: Iceberg,Hudi,Paimon have different backends. They may need different implement for different backends.
Describe the proposal
Gravitino unified authorization will use multiple authorization plugins for different catalogs. For relational catalogs, they usually supports
GRANT/REVOKE
SQL to authorize.The plugin will support use SQL to authorize. In Gravitino, we have three kinds of relational catalog.
I will draft a design document first.
Task list
The text was updated successfully, but these errors were encountered: