Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14181

Investigate changes in SERVER-50993: Audit dropCollection for views

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Sprint:
      ServerDocs2020: Mar9 - Mar16, ServerDocs2020: Mar16 - Mar23, ServerDocs2020: Mar23 - Mar30, ServerDocs2020: Mar30 - Apr06, ServerDocs2020: Apr6 - Apr13

      Description

      Description

      Downstream Change Summary

      This ticket requires changes for the `dropCollection` atype on the "System Event Audit Messages" docs page (https://docs.mongodb.com/manual/reference/audit-message/#audit-action-details-results).
      Specifically, the `dropCollection` atype is now used to audit both collections and views that have been dropped. If the `dropCollection` atype refers to a collection, then the param is the same as now. If the `dropCollection` atype refers to a view, then the param will include:

      Unknown macro: { ns}

      Additionally, the result code for `dropCollection` may be 0 - Success or 26 - NamespaceNotFound in case the provided collection or view namespace to drop doesn't exist.

      Description of Linked Ticket

      null

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dave.cuthbert Dave Cuthbert
              Reporter:
              backlog-server-pm Backlog - Core Eng Program Management Team
              Participants:
              Last commenter:
              Dave Cuthbert Dave Cuthbert
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                6 days ago
                Date of 1st Reply: