vinishjail97 opened a new issue, #643:
URL: https://github.com/apache/incubator-xtable/issues/643

   ### Feature Request / Improvement
   
   Today, numerous catalogs have emerged, each with its own specifications for 
table creation, metadata refreshing, and implementing data governance rules. 
This diversity has led to increased complexity and confusion, making it 
challenging for users to choose the right catalog. To address this challenge, 
we previously proposed an 
[RFC](https://github.com/apache/incubator-xtable/pull/605/files) for 
synchronizing table format metadata across catalogs.
   
   An access control policy defines a rule stating, "A principal has specific 
privileges for a securable object." In the context of data catalogs, these 
privileges can include actions like SELECT or CREATE statements used in DDL, 
DML, or DQL queries, the securable objects can range from databases and tables 
to columns and beyond. When a catalog is connected to a query engine, it 
enforces these permissions for the principal (user) either directly or by 
issuing temporary credentials that the query engine can use to execute queries 
securely.
   
   In today’s data ecosystem, numerous catalogs exist, each with its own 
specifications and methods for enforcing access control policies. Some 
catalogs, like AWS Glue and BigLake, are tightly integrated within their 
ecosystems, while others rely on credential-sharing approaches to support 
multiple query engines. Similar to how we have defined 
[InternalTable](https://github.com/apache/incubator-xtable/blob/main/xtable-api/src/main/java/org/apache/xtable/model/InternalTable.java),
 we aim to establish a canonical representation for access control policies and 
synchronize these policies across different catalogs.
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
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