[SERVER-49837] add test for createIndexes command to check if all indexes already exist under an intent lock Created: 23/Jul/20  Updated: 27/Oct/23  Resolved: 19/Oct/21

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

Type: Improvement Priority: Minor - P4
Reporter: Benety Goh Assignee: Gabriel Marks
Resolution: Gone away Votes: 0
Labels: neweng, techdebt
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-49415 create_new_indexes_with_conflict.js h... Closed
is related to SERVER-44405 Use MODE_IX lock for implicit collect... Closed
Sprint: Execution Team 2021-11-01
Participants:

 Description   

The createIndexes command checks the requested index specs against the existing indexes in the catalog under an intent lock. We should ensure that we have test coverage over this code path (either by extending an existing test or adding a new test script).

The JS test create_new_indexes_with_conflict.js was originally introduced in SERVER-44405 to cover this test case, but we discovered this was not the case in SERVER-49415.



 Comments   
Comment by Gabriel Marks [ 19/Oct/21 ]

This test already exists: https://github.com/mongodb/mongo/blob/bf4cd96645253bb29a32ec0568095049bc49ab77/jstests/noPassthroughWithMongod/create_existing_indexes_no_conflict.js

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