[BUG]: remove leading slash from version file name #4236
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 changes
Minio and S3 treat leading in keys differently. Minio strips the leading slash, S3 does not. This means that attempting to look up the key
/foo
fors3://sample-bucket/foo
fails, but succeeds when testing locally with Minio.This materializes as the garbage collector being unable to fetch version files in staging.
I will update the
collections.version_file_name
column in staging after merge to manually remove the leading slash.Test plan
How are these changes tested?
I connected to the Postgres sysdb in my local environment and verified that version file names are now saved without a slash prefix.