be20fb80e4
This is a prerequisite of #42189: * Add directory delete method to blob container specific to each implementation: * Some notes on the implementations: * AWS + GCS: We can simply exploit the fact that both AWS and GCS return blobs lexicographically ordered which allows us to simply delete in the same order that we receive the blobs from the listing request. For AWS this simply required listing without the delimiter setting (so we get a deep listing) and for GCS the same behavior is achieved by not using the directory mode on the listing invocation. The nice thing about this is, that even for very large numbers of blobs the memory requirements are now capped nicely since we go page by page when deleting. * For Azure I extended the parallelization to the listing calls as well and made it work recursively. I verified that this works with thread count `1` since we only block once in the initial thread and then fan out to a "graph" of child listeners that never block. * HDFS and FS are trivial since we have directory delete methods available for them * Enhances third party tests to ensure the new functionality works (I manually ran them for all cloud providers) |
||
|---|---|---|
| .. | ||
| aggs-matrix-stats | ||
| analysis-common | ||
| ingest-common | ||
| ingest-geoip | ||
| ingest-user-agent | ||
| lang-expression | ||
| lang-mustache | ||
| lang-painless | ||
| mapper-extras | ||
| parent-join | ||
| percolator | ||
| rank-eval | ||
| reindex | ||
| repository-url | ||
| transport-netty4 | ||
| build.gradle | ||