gandola opened a new issue, #14336: URL: https://github.com/apache/iceberg/issues/14336
### Query engine Spark and Trino ### Question Hi, I'm implementing a small solution where I have spark streaming committing micro-batches into some Iceberg tables. Due to the nature of the system, we don't need time-travel, users should see the data on its current/latest snapshot. I was thinking to keep as less history as possible and I'm doing the following: ``` write.metadata.delete-after-commit.enabled=true write.metadata.previous-versions-max=1 history.expire.max-snapshot-age-ms=1 commit.manifest.min-count-to-merge=1 ``` Do you see any negative impact on this set of table configurations either on potential table corruption (e.g: during concurrent actions like "data files rewrite" since I'm using MoR) or any performance impact on commit? Maybe the `commit.manifest.min-count-to-merge` should be higher to do it less times instead of each commit? Do you have any other suggestion for these types of use cases that could help the performance overall? Thank you Cheers -- 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]
