Do not set scheme if unset #667
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.
Before this PR
StandaloneEncryptedFileSystem#setUriSchemeFunc will always set the uri's scheme, even if it's not already set.
After this PR
We only set the scheme if it's already set. This matches the behavior of this class in 2.9.2: https://github.com/palantir/hadoop-crypto/pull/442/files#diff-050a60db63beecf42d4d99e5e9132ee7f6dc68ae9b552e37ff5ccd2a109806d6L166
==COMMIT_MSG==
StandaloneEncryptedFileSystem returns to its old behavior, of only overriding the scheme when the uri uses a scheme
==COMMIT_MSG==
Possible downsides?