jackye1995 commented on pull request #4280: URL: https://github.com/apache/iceberg/pull/4280#issuecomment-1061344862
> Plus enforcement can't really be done client side. > I don't think this should change the Table API. Yes agree, please hold on the review for some time, I am asking for an initial draft from @xiaoxuandev so we can just openly review the code changes. I think this needs a few iterations to trim down the changes. We should be able to make this feature work through just creating the correct TableOperation object using the correct credentials. I don't even think we need a `LakeFormationCatalog`, it can just be controlled through a flag. > I'm also curious about the long-term plan for access control integration because I don't think we want to put very many features in Iceberg for it. I think database and table level access control is most likely going to be all we add in Iceberg. For column-level and cell-level access control, all the AWS compute platforms are mostly already onboard with that, and there is guidelines published now for any third-party integration, it's not something that could be enforced just within the table format itself. -- 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]
