Retry attempts should share a single stable operation_id

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • Python Drivers
    • Hide

      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?

      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • None
    • None
    • None
    • None
    • None
    • None

      Command-monitoring events carry an operation_id to correlate the events of one operation. For single-document CRUD and cursor operations, each retry attempt gets a different operation_id (it defaults to the per-attempt request_id), so consumers can't group a retried operation's events. Bulk writes already share one across batches.

            Assignee:
            Shrey Varma
            Reporter:
            Shrey Varma
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: