Repair incorrect callback behavior during persistence operations

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Done
    • Priority: Major - P3
    • 8.0.1
    • Affects Version/s: None
    • Component/s: None
    • Persistence Callbacks
    • None
    • Done
    • None
    • 3
    • 1
    • 3
    • 150
    • None
    • Hide

      Summary: This epic encompasses ensuring the callbacks see the correct data during persistence operations, are called at appropriate times, and that the correct callbacks are invoked.

      Engineers: Neil Shweky, Dmitry Rybakov
      2022-02-24: Setting Target date to 2022-03-04

      • Dmitry and Neil are making very quick progress on the outstanding tickets in this long-standing epic. No timeline concerns here.
      • This is being worked on in parallel with MONGOID-4639, which also addresses persistence improvements.
      Show
      Summary: This epic encompasses ensuring the callbacks see the correct data during persistence operations, are called at appropriate times, and that the correct callbacks are invoked. Engineers: Neil Shweky, Dmitry Rybakov 2022-02-24: Setting Target date to 2022-03-04 Dmitry and Neil are making very quick progress on the outstanding tickets in this long-standing epic. No timeline concerns here. This is being worked on in parallel with MONGOID-4639 , which also addresses persistence improvements.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This epic encompasses ensuring the callbacks see the correct data during persistence operations, are called at appropriate times, and that the correct callbacks are invoked.

              Assignee:
              Dmitry Rybakov
              Reporter:
              Oleg Pudeyev (Inactive)
              Bernie Hackett Bernie Hackett
              Alexander Golin Alexander Golin (Inactive)
              Rachelle Palmer Rachelle Palmer
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved:
                2 weeks, 2 days
                None
                None
                None
                None