mongo.newClient should apply clientOpt.TopologyOptions last, not first

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Options & Configuration
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, in mongo.newClient the user defined topology options are set first, which means options set by the configuration string, like Handshaker will be overwritten.

      To fix this, we should prepend the two options that are specified instead of appending them.

              Assignee:
              Unassigned
              Reporter:
              Kristofer Brandow (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: