Remove the obsolete 235-byte namespace limit for sharded collections

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 2
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      MongoDB currently permits explicitly created namespaces up to 255 bytes. However, sharded collections remain limited to 235 bytes because older server versions persisted per-shard filtering metadata in namespace-suffixed collections using the config.cache.chunks.<namespace> prefix. That persisted cache is no longer required after the Shards Authoritative work, but the 235-byte validation remains.

      This leaves sharded collections with a lower limit than unsharded collections, even though both are otherwise governed by the 255-byte explicit-namespace limit.

      The goal is to remove the obsolete 235-byte restriction for sharded collections (in version 10.0) and allow explicitly created sharded namespaces up to the full 255-byte limit.

            Assignee:
            Unassigned
            Reporter:
            Antonio Fuschetto
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: