singhpk234 opened a new pull request, #13810: URL: https://github.com/apache/iceberg/pull/13810
### About the change This change proposes loaded-via in loadTable request, which is expected to contain the FQN of the view (only 2 part identifier), which a rest catalog would expect from the client based on that it knows the table is being loaded in the context of view (view referencing the table) so that table can an action accordingly. This would be really helpful in following cases : Supporting the security for views, i.e definer / invoker mode : `Definer` mode means the access to table should be authorized against the principal which created the view, this will be a very normal case where one would want to create a view and grant access to view but not to the underlying table. `Invoker` mode means the access to table should be authorized against the principal which which is calling the loadTable essentially what happens in default. when a view is defined in a definer mode security, `loaded-via` would help give catalog proper signal that this loadTable is happening in the context of view (i.e view is referencing the table) so the catalog can reverse lookup who the creator was and what the security mode is defined, and take proper authZ action. ### Reference Implementation TODO: trying spark The problem is SparkCatalog when doing loadTable just get the identifier, the view context which we got in the analysis phase need to made passed through all the way to icebergCatalog it hold, i have an option with SparkSession.getActive() in the spark Catalog and set in the session context to be used to making the call, still thinking of something better, -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
