[SERVER-56918] Add create index to DDL FSM workloads Created: 13/May/21 Updated: 06/Dec/22 Resolved: 12/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding EMEA
|
| Participants: |
| Description |
|
We have 4 type of concurrency tests regarding DDL: However, a create index could implicitly create a collection, and this is not being tested anywhere. We should add a create index state to the DDL + CRUD test. |
| Comments |
| Comment by Connie Chen [ 12/Nov/21 ] |
|
After inspecting the code, we realized that the code coverage will not increase materially. |
| Comment by Marcos José Grillo Ramirez [ 20/Sep/21 ] |
|
kaloian.manassiev the createIndexes path uses a slightly different library than the write path, although, in the end, the same function is being called. I would say, by adding the createIndex command to the FSM tests, we would increase code coverage. |
| Comment by Kaloian Manassiev [ 17/Sep/21 ] |
|
marcos.grillo, is there something special about createIndex which makes it any different than implicit collection creation due to insert in a non-existent collection? |