yuqi1129 commented on code in PR #11629:
URL: https://github.com/apache/gravitino/pull/11629#discussion_r3404204315


##########
design-docs/starrocks-authorization-pushdown.md:
##########
@@ -0,0 +1,248 @@
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one
+  or more contributor license agreements.  See the NOTICE file
+  distributed with this work for additional information
+  regarding copyright ownership.  The ASF licenses this file
+  to you under the Apache License, Version 2.0 (the
+  "License"); you may not use this file except in compliance
+  with the License.  You may obtain a copy of the License at
+
+   http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing,
+  software distributed under the License is distributed on an
+  "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+  KIND, either express or implied.  See the License for the
+  specific language governing permissions and limitations
+  under the License.
+-->
+
+# Design: StarRocks Authorization Pushdown
+
+## 1. Problem Statement and Goals
+
+### 1.1 Problem
+
+Apache Gravitino supports metadata management for StarRocks through the 
`jdbc-starrocks`
+catalog, but it does not yet push Gravitino authorization changes into 
StarRocks native
+authorization. When users create roles, grant privileges or assign roles to 
users or groups, 
+StarRocks does not automatically receive the corresponding users, roles, 
grants, revokes, 
+or ownership changes.
+
+This creates a gap between the Gravitino authorization model and the access 
control that
+StarRocks enforces when users query StarRocks directly. StarRocks already has 
a SQL-based

Review Comment:
   We may need to consider that users may change privileges without using 
Gravitino since they can query data from StarRocks directly, so how do we 
synchronize the privileges data? 



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to