[SERVER-67801] createIndexes should handle empty index specs on config.transactions Created: 06/Jul/22  Updated: 29/Oct/23  Resolved: 12/Jul/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.0.1, 6.1.0-rc0

Type: Bug Priority: Major - P3
Reporter: Benety Goh Assignee: Benety Goh
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-67991 clean up create_indexes.js Closed
is related to SERVER-66565 Create config.transactions partial in... Closed
is related to SERVER-32043 Disallow users from creating new inde... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v6.0
Sprint: Execution Team 2022-07-25
Participants:
Linked BF Score: 17

 Description   

The createIndexes is expected to check for and reject an empty list of index specs (with an error code of BadValue provided in the indexes field. This handling currently does not extend to the internal collection config.transactions.

There is also a case to be made for returning IllegalOperation when we pass an empty list of specs to createIndexes because this is the behavior established in SERVER-32043 in 4.0.



 Comments   
Comment by Githook User [ 27/Jul/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-67801 createIndexes on config.transactions should handle empty list of index specs

(cherry picked from commit a7cd9bf337b0c41387ebc351e41093d3ff5aba59)
Branch: v6.0
https://github.com/mongodb/mongo/commit/489a83cb9f8bde7c687c477a7c87be8abea80776

Comment by Githook User [ 12/Jul/22 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-67801 createIndexes on config.transactions should handle empty list of index specs
Branch: master
https://github.com/mongodb/mongo/commit/a7cd9bf337b0c41387ebc351e41093d3ff5aba59

Generated at Thu Feb 08 06:09:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.