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

[createIndex response format] mongos createIndex should prioritize other errors over CannotImplicitlyCreateCollection

    XMLWordPrintableJSON

Details

    • Sharding
    • ALL
    • Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25

    Description

      Currently, if shard returns multiple errors, createIndex simply selects the first error it saw and puts it on the top level error field. Instead, it should prioritize other errors over CannotImplicitlyCreateCollection.

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-38367 Descriptive error message for the inability to create unique indexes on arbitrary fields in sharded collections

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Task - A task that needs to be done. SERVER-43490 Validate if we can perform TODO listed in SERVER-38686

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-sharding Backlog - Sharding Team
              randolph@mongodb.com Randolph Tan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: