Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15731

[Server] Investigate changes in SERVER-68769: If a shard key index cannot be dropped then a user should not be able to hide that index

    XMLWordPrintableJSON

Details

    • Hide
      At the Shard Key Indexes documentation it is written: "If you drop the last valid index for the shard key, recover by recreating an index on just the shard key". It is not valid anymore.
      In addition, we should specify that it is not possible to drop or hide the last valid index for the shard key.
      Show
      At the Shard Key Indexes documentation it is written: "If you drop the last valid index for the shard key, recover by recreating an index on just the shard key". It is not valid anymore. In addition, we should specify that it is not possible to drop or hide the last valid index for the shard key.
    • true

    Description

      Original Downstream Change Summary

      At the Shard Key Indexes documentation it is written: "If you drop the last valid index for the shard key, recover by recreating an index on just the shard key". It is not valid anymore.
      In addition, we should specify that it is not possible to drop or hide the last valid index for the shard key.

      Description of Linked Ticket

      A hidden index helps users evaluate the potential impact of dropping an index without actually dropping the index. That way, the user can just unhide the index if the impact is bad. Hidden and dropped indexes should therefore have the same behavior.

      For sharding, however, we allow a shard key index that cannot be dropped to be hidden. In order to maintain consistency, we should not allow users to hide a shard key index that cannot be dropped.

      Attachments

        Issue Links

          Activity

            People

              ian.fogelman@mongodb.com Ian Fogelman
              backlog-server-pm Backlog - Core Eng Program Management Team
              Ian Fogelman Ian Fogelman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                3 weeks, 2 days ago