MCOL-3488. Writeengine getting IDB-FS an odd way #857
Merged
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
added 3 commits
September 9, 2019 09:54
The ChunkManager class was getting an IDBFileSystem instance in a different way than seemingly everything else. Added code to allow it to get an SMFileSystem if cloud storage is specified.
LinuxJedi
approved these changes
Sep 9, 2019
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.
Found that writeengine was getting an IDBFilesystem instance in a way different than other components. Errors would only show up during test112, when a compression chunk needs to expand (lots of updates in the same region of the table).
Made those instances get an SMFilesystem (the cloud type) instance when appropriate.