Disallow nesting of RouterRoles for the same namespaces

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Catalog, Sharding
    • None
    • Catalog and Routing
    • 2
    • 🟩 Routing and Topology
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket is to add logic to disallow nesting of RouterRoles that operate on the same namespaces. Nesting will be defined as having two RouterRole objects on the same operation context that:

      • Mix database and collection routing: Database routing is intended for DDL operations and should not be mixed with CRUD
      • The same databases (for database routing)
      • Overlapping namespaces (for collection routing)

      Given that the Router objects are now stateful, we will also ban having two objects coexist on the same stack.

            Assignee:
            Unassigned
            Reporter:
            Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: