[SERVER-63871] Log 'idIndex' field in the oplog for create operation when using v:1 index Created: 22/Feb/22  Updated: 25/Jul/23

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

Type: Improvement Priority: Major - P3
Reporter: Arun Banala Assignee: Backlog - Storage Execution Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Storage Execution
Participants:

 Description   

If a create command requests for a v:1 _id index, using the idIndex parameter, we don't seem to be logging the _id index specification in the oplog. Since we are now exposing the create operation in the change stream events(which relies on oplog to fetch the command specification), it would be good we can log the index spec for v:1 index, as we do when it's v:2 index.

Additionally, we are also ignoring the idIndex.name parameter (for both v:1 and v:2) for create.command, which could be misleading for the users. We should either disallow users from specifying it, or store the user provided name.



 Comments   
Comment by Connie Chen [ 08/Mar/22 ]

michael.gargiulo - any concerns disallowing the creation of v:1 indexes

Comment by Louis Williams [ 22/Feb/22 ]

Could we alternatively deprecate support for v:1 indexes?

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