Fix non-determinism in a merge test

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Atlas Streams
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In the following two tests in merge.js, the order in which records get inserted is non-deterministic when parallel merge writers are present. So the assertions in these tests should not depend on a specific value of the `a` field

      testKeepExistingInsertMode()
      testDynamicTarget()

      There might be other tests in the file too that fail similarly.

      More context in this slack thread.

              Assignee:
              Matthew Normyle
              Reporter:
              Mayuresh Kulkarni
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: