Conversation
|
|
||
| def test_invalidate_all(): | ||
| """Cache is entirely invalidated.""" | ||
| cache.invalidate_all() |
There was a problem hiding this comment.
It's a smoke test. I'm inclined to rely on GDAL's testing. invalidate_all() simply calls a GDAL method with no arguments. There's no way to use it wrongly. invalidate() uses the same path parsing pattern used elsewhere in rasterio. It's reliable.
|
@snowman2 @vincentsarago I'm glad we agree! I'd like to improve the documentation. The exact semantics of @rouault can you explain the nuances of the function? For example, does the prefix |
does OSGeo/gdal#11493 clarify things? |
4 participants
I like "invalidate" as a method name. These two methods help solve the problem pointed out in the last sentence of RFC 9111 Section 4.4. If you combine Rasterio with, say, uploading files to S3 using boto3, those PUTs don't go through Rasterio's cache and thus can't be smartly invalidated.
Resolves #3275