Remove collection name limit of 235 for sharded collections

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • 3
    • None
    • 3
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-89138 added a limitation to the number of characters in collection names for sharded collections, however, this is an arbitrary length that does not match the current internal limit of 255 added by SERVER-46641.

      The purpose of this ticket is to remove the collection name limit for sharded collections, ensuring that on downgrade, setFeatureCompatibilityVersion will fail to downgrade if we find sharded collections with collection names higher to the limit present in the previous version.

              Assignee:
              Unassigned
              Reporter:
              Marcos José Grillo Ramirez
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: