summaryrefslogtreecommitdiff
path: root/src/mongo/db/sessions_collection_sharded.cpp
diff options
context:
space:
mode:
authorJustin Seyster <justin.seyster@mongodb.com>2017-08-31 15:44:35 -0400
committerJustin Seyster <justin.seyster@mongodb.com>2017-08-31 15:44:35 -0400
commited619087e8dc51eb13578f5ebdd60f8ffee750aa (patch)
treeb4e71905ab9906a7cea24873a2269de81cbe1cdd /src/mongo/db/sessions_collection_sharded.cpp
parent2d568c4ddbe9065d92a5f0443d0c65c8f3a62a87 (diff)
downloadmongo-ed619087e8dc51eb13578f5ebdd60f8ffee750aa.tar.gz
jseyster/json-schema-feature-compatibility-2
If a user updates a 3.4 node to 3.6 but keeps the feature compatibility version at 3.4, it should remain possible to be in a replica set with 3.4 nodes or even to downgrade back to 3.4. To that end, we ensure that is not possible to create a collection validator with a $jsonSchema expression unless the feature compatibility version is 3.6. A $jsonSchema validator would not replicate correctly to a 3.4 node, and its existence in the database would prevent a downgrade to 3.4.
Diffstat (limited to 'src/mongo/db/sessions_collection_sharded.cpp')
0 files changed, 0 insertions, 0 deletions