BatchedDeleteStage can sometimes not find the record it is deleting

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • Execution Team 2024-11-11, Execution Team 2024-12-23, Execution Team 2025-01-06, Execution Team 2025-01-20
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      In rare circumstances, it is possible for BatchedDeleteStage to enqueue the same document twice for deletion and then attempt two deletes of that document, with the second attempt triggering an unnecessary warning.

      When refactoring BatchedDeleteStage for this project, we should add logic to prevent already enqueued documents from getting added to the queue a second time.

            Assignee:
            Unassigned
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: