kinolaev commented on issue #11648: URL: https://github.com/apache/iceberg/issues/11648#issuecomment-5441510246
> this doesn't really make sense for position delete files @RussellSpitzer, just curious, why wouldn't it make sense? A position delete file contains deletes for many data files, and per my benchmark results, caching the whole file can be almost as fast as a single selective read (default settings + the rehashing issue fixed). With the default target delete file size at 64 MB, position delete files are most probably referenced by multiple data files. This means that whenever a read operation (not only compaction) requires at least two data files referencing the same position delete file, the cache speeds up the operation. Am I missing something? Again - just curious to understand, as I don't currently use position deletes myself. -- 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]
