applyOps should return NamespaceNotFound when applying a CRUD operation on a non-existent collection/database

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 3.4.10, 3.6.0-rc0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently applyOps relies on lower level subsystems such as the catalog or query execution subsystem to handle CRUD operations that refer to non-existent collections or databases. Some CRUD operations, such as update/upserts, may implicitly create a collection as a result. We should uniformly reject any CRUD operations on non-existent namespaces in apply_ops.cpp (within the _applyOps() function).

            Assignee:
            Benety Goh
            Reporter:
            Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: