Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-95764

Make the failure behavior of performDeletes and performUpdates consistent when called with a time-series source on a missing collection

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution

      When performDeletes() and performUpdates() are called with a time-series source on a missing collection, the delete fails with the message "
      Catalog changed during operation, could not find time series buckets collection for write," while the update path fails with NamespaceNotFound. It may be clearer to make the failure behavior of these functions (under the same conditions) more consistent (inserts and updates both fail with NamespaceNotFound).
      For update, the collection acquisition lambda checks immediately after whether the collection exists and asserts if not.

      For delete, the collection acquisition is passed to a checking function that asserts with a different message once it realizes the collection doesn't exist.

      See the TODO(s) marked with this ticket number for anticipated test breakages should the failure behavior be changed.

            Assignee:
            Unassigned Unassigned
            Reporter:
            malik.endsley@mongodb.com Malik Endsley
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: