[SERVER-52929] Correctly handle compound indexes with 32 keys Created: 18/Nov/20  Updated: 29/Oct/23  Resolved: 07/Dec/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 4.2.1, 4.4.0
Fix Version/s: 4.9.0, 4.4.3, 4.2.12

Type: Bug Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4, v4.2, v4.0, v3.6
Sprint: Execution Team 2020-12-14
Participants:
Case:
Linked BF Score: 19

 Description   

We do not properly handle compound indexes that have 32 keys.

This problem may result in one of the following errors: "Overflow: Ordering offset is out of bounds: 32" or "Location50811: Unknown type: 251".



 Comments   
Comment by Githook User [ 10/Dec/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-52929 Correctly handle compound indexes with 32 keys

(cherry picked from commit 957ddd678dbd49a96318a13e8f669567e4eba3ab)
(cherry picked from commit 2faadd670bd54e7112c4fec6f6abc011d38b912c)
Branch: v4.2
https://github.com/mongodb/mongo/commit/1c35a911de679fef5f64cb76e0bfd2acfa44c267

Comment by Githook User [ 09/Dec/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-52929 Correctly handle compound indexes with 32 keys

(cherry picked from commit 957ddd678dbd49a96318a13e8f669567e4eba3ab)
Branch: v4.4
https://github.com/mongodb/mongo/commit/2faadd670bd54e7112c4fec6f6abc011d38b912c

Comment by Githook User [ 07/Dec/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-52929 Correctly handle compound indexes with 32 keys
Branch: master
https://github.com/mongodb/mongo/commit/957ddd678dbd49a96318a13e8f669567e4eba3ab

Generated at Thu Feb 08 05:29:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.