[SERVER-36281] Test upgrade/downgrade behaviors for unlimited index key length Created: 25/Jul/18  Updated: 29/Oct/23  Resolved: 22/Aug/18

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.3

Type: Task Priority: Major - P3
Reporter: Xiangyu Yao (Inactive) Assignee: Xiangyu Yao (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36228 Extend the size of TypeBits in KeyString Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-08-27
Participants:
Linked BF Score: 13

 Description   

Things to test include:

  1. MongoDB 4.2 (FCV 4.0) and MongoDB 4.0 allow reading and deleting long (unique) index keys but does not allow inserting or updating long (unique) index keys.
  2. MongoDB 4.2 (FCV 4.2) allows inserting, reading, deleting and updating long (unique) index keys.
  3. MongoDB 4.0 throws warning on startup when detecting the new feature tracker bit.
  4. MongoDB 4.2 could successfully validate index consistency after reindex() if 4.0 intentionally missed out long index keys by setting 'failIndexKeyTooLong' to false.
  5. MongoDB 4.0 could successfully validate index consistency after drop() if 4.2 inserted long index keys (with < 127 bytes typebits).


 Comments   
Comment by Githook User [ 22/Aug/18 ]

Author:

{'name': 'Xiangyu Yao', 'email': 'xiangyu.yao@mongodb.com', 'username': 'xy24'}

Message: SERVER-36281 Test upgrade/downgrade behaviors for unlimited index key length
Branch: master
https://github.com/mongodb/mongo/commit/0d5d976fbcd05cc8ed29b866da35861a91358415

Generated at Thu Feb 08 04:42:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.