Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-63871

Log 'idIndex' field in the oplog for create operation when using v:1 index

    XMLWordPrintable

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • None

    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.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

              Created:
              Updated: