Re: [Discuss] Document Snapshot Summary Optional Fields for Standardization

Hi everyone, Happy new year! I've updated the proposal and PR with the optional snapshot summary fields documented in a new Appendix in table spec and addressed review comments. You can find the links below: - proposal doc

Re: [Discussion] Maintain vendor neutrality on the quickstart page

I also think that is a good idea and interested to take this up. But before I do so, here are couple clarifications i would like. Based on what I recalled from tabulario/spark-iceberg, it has couple additional things are not there compared to official spark image: 1. couple additional python lib

Re: Changing default delete file granularity for Spark writes from partition to file scoped

I think that makes sense to do, I'll do a review this morning On Mon, Dec 23, 2024 at 9:53 AM Amogh Jahagirdar <2am...@gmail.com> wrote: > Hey all, it's been a while but I wanted to follow up on this thread in > case there were any remaining thoughts on changing the default write > granularity in

Re: There is no easy way to secure Iceberg data. How can we improve?

if the data is stored in S3 then if someone has unrestricted access to a single store containing all the data (default without S3 access grants, cloudera ranger extensions or some other access control mechanism to grant access to clients without sharing credentials) - then it's effectively impossib

Re: There is no easy way to secure Iceberg data. How can we improve?

Hi Vladimir, Thanks for starting this discussion. I agree with you that the REST catalog "should" be the centralized security mechanism (Polaris is a good example). However, we have two challenges today: - there's no enforcement to use the REST catalog. Some engines are still directly accessing t