amogh-jahagirdar commented on issue #12590: URL: https://github.com/apache/iceberg/issues/12590#issuecomment-2741215904
I think the intention of that threadpool is a bit different than what you're thinking. `DELETE_WORKER_POOL` is meant for reading delete files concurrently into in-memory structures (which are later used for indicating if a given file path/position or equality predicate is deleted). It's not intended for issuing the physical delete against the file system which is what the referenced code path is doing. That said, if you've seen performance or reliability issues with using the normal worker thread pool for issuing deletes, would be interested in hearing more! -- 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 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