vigneshc commented on issue #12263: URL: https://github.com/apache/iceberg/issues/12263#issuecomment-3700232149
RBAC is one of the main gaps. I don't think we can restrict write access just to a branch today. I believe this would be a catalog feature. Would making RBAC branch aware fit with the design? -------------- Exploring the alternative, of making clone a separate concept below. Should we listing down the use cases that clone is targeting and be explicit about the ones it isn't? Initial issue description listed the use cases. I see two large classes 1. Experimentation, testing. 2. Clone, and evolve independently. Is keeping the ownership of data files with parent table, and letting the cloned table break an issue for testing and experimentation? Can we add an explicit property to the cloned table indicating that its data files are referenced? We could then add a procedure, that does a deep clone, by making a copy of the data files for use case 2. -- 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]
