[BREAK] Remove support of MongoDB 3.2 and deprecate MongoDB 3.4 #15199
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
|
Damn :-( |
rodrigok
approved these changes
Aug 19, 2019
|
@sampaiodiego shouldn't we title this as |
|
Agreed @rodrigok |
sampaiodiego
changed the title
sampaiodiego
changed the title
|
Ahhh. Relief :-) A bit more time. This may want a bit of thought as there is no simple leap from 3.4 -> 4.x |
|
right @reetp .. you have to upgrade "step-by-step", that means from 3.2 to 3.4 and then 3.4 to 3.6 and so on |
Merged
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.
Also add env var flags to bypass validations:
BYPASS_OPLOG_VALIDATIONBYPASS_NODEJS_VALIDATIONBYPASS_MONGO_VALIDATIONWhere do you guys think we can add those to our docs?