w14 opened a new issue, #9112: URL: https://github.com/apache/iceberg/issues/9112
The docs discuss time travel but not the performance / size requirements. 1. Does Iceberg store changes by row or whole table? So if you have a 100MiB table and you make 100 separates changes (inserts, updates deletes) of 1 row each containing 1KiB, will the total storage on s3 by 100MiB + O(100 * 1KiB) or O(100 * 100MiB)? 2. Is it recommended to track every change (like row level changes) over months or years? Is there some checkpointing? -- 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: issues-unsubscr...@iceberg.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
