Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-143

Don't include the nModified field in Bulk API results if talking to a legacy server.

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: None
    • Labels:
      None
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      PYTHON-647 Done 2.7
      JAVA-1134 Done 2.12.0
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion PYTHON-647 Done 2.7 JAVA-1134 Done 2.12.0

      Clarification to the Bulk API: We should not include the nModified field in Bulk API results if we're talking to a legacy server.

      Prior, it was left unspecified whether nModified should be included or not when talking to a legacy server. Now, we're saying it should definitely not be included. If your language is constrained such that you must include the field, then user code should get an exception when accessing the field if you're talking to a legacy server.

      (This ticket is only about merging results with the Bulk API. DRIVERS-144 is about results from a single direct call to Collection.update().)

            Assignee:
            barrie Barrie Segal
            Reporter:
            barrie Barrie Segal
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: