Add ETag into DiskDataCache hashed block path #594
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of change
We discussed in #593 to hash the S3 key, ETag, and possibly block ID together when defining a path for the disk-based data cache. This is the PR that implements that change.
I'm encoding only the ETag as I still see value in keeping the block ID visible in the path. This allows us to do things like invalidate all of the blocks for a given S3 object version (version defined by its ETag).
Previous discussions:
Relevant issues:
Does this change impact existing behavior?
No change to released behavior. This changes file paths for the blocks on disk for the data cache, which is behind a build-time feature flag.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).