|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!
|
|
Author:
{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}
Message: SERVER-58571 fix test to match config.cache.collections IDL
Branch: master
https://github.com/mongodb/mongo/commit/6232caba341d286d17e214e6f5a159d09a23de3c
|
|
Author:
{'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}
Message: SERVER-58571 shardCollection command should enable the long names support by default in 5.1 FCV
Branch: master
https://github.com/mongodb/mongo/commit/cf2e19f7432ebe3a5e28b0dbc3eab6b1b5e53ec1
|
|
The logic I have in mind to implement when the collection metadata is created can be summarized as follows:
if (currentFCV >= 5.1)
|
collection.supportingLongName = implicitly_enabled
|
else if (globalConf.supportLongName)
|
collection.supportingLongName = explicitly _enabled
|
else
|
// nothing, collection.supportingLongName = none
|
|
Generated at Thu Feb 08 05:44:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.