Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-20744

Remove redundant code paths for setting a Value in a MutableDocument

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • 3.1.8
    • None
    • Query Execution
    • Fully Compatible

    Description

      Currently there are a couple ways to set a field of a MutableDocument to a new value. The only one two that are move optimized are:

      doc.getField(fieldName) = Value(val);
      doc.getNestedField(fieldName) = Value(val);
      

      We should remove all variants of MutableDocument::setField and MutableDocument::setNestedField in favor of the above strategy. We should also remove MutableDocument::getField in favor of MutableDocument::operator[]

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: