DM-31398: Handle absolute URIs in datastore with transfer=None export #559
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously this worked for local file systems because uri.path returns an absolute path and the system didn't notice the bad logic. At IDF storing uri.path for an absolute URI gives the path component "/CALIB/..." and drops the scheme and bucket name. Now correctly trap an absolute URI with None transfer mode.
hsinfang
approved these changes
Aug 14, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Previously this worked for local file systems because uri.path
returns an absolute path and the system didn't notice the
bad logic. At IDF storing uri.path for an absolute URI gives
the path component "/CALIB/..." and drops the scheme and bucket
name. Now correctly trap an absolute URI with None transfer
mode.
Checklist
doc/changes