Optimize the migration cloner op-observer for higher insertion speed

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • CAR Team 2025-11-10, CAR Team 2025-11-24
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      A quick POC proved the migration cloner opbserver can be optimized in terms of speed (and as consequence, the write path)
      The logic adds a new change for every document but the information seems to be useful only in case we actually have a cloning in process 
      We can avoid inserting this information at all

            Assignee:
            Enrico Golfieri
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: