[SERVER-42067] Ensure key Ordering offset does not exceed the maximum number of compound index keys Created: 03/Jul/19  Updated: 29/Oct/23  Resolved: 05/Aug/19

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.2.1, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: execution_intern_2019
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Execution Team 2019-08-12
Participants:
Case:

 Description   

To prevent undefined behavior, throw an exception in Ordering::get() to ensure the requested Ordering offset remains below 32 bits, the existing limit of the number of fields in a compound index key.



 Comments   
Comment by Githook User [ 14/Aug/19 ]

Author:

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

Message: SERVER-42067 Ensure key Ordering offset does not exceed the maximum number of compound index keys

(cherry picked from commit fe4ca9897f8b8e91dc82fc15250e287da68cc83f)
Branch: v4.2
https://github.com/mongodb/mongo/commit/37d64e82e8a97475ef49fa94a9cd610d35cfda17

Comment by Githook User [ 05/Aug/19 ]

Author:

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

Message: SERVER-42067 Ensure key Ordering offset does not exceed the maximum number of compound index keys
Branch: master
https://github.com/mongodb/mongo/commit/fe4ca9897f8b8e91dc82fc15250e287da68cc83f

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