Spec compliance for limit and batchSize

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: CRUD
    • None
    • None
    • Java Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      It appears that the java driver is out of specification for getMores and setting of batchSize.

      The following tests have been skipped due to non compliance:

      • def.skipNoncompliant("The driver doesn't reduce the batchSize for the getMore")
        .test("command-logging-and-monitoring/tests/monitoring", "find",
        "A successful find event with a getmore and the server kills the cursor (<= 4.4)");
      • def.skipNoncompliant("The driver doesn't reduce the batchSize for the getMore")
        .test("atlas-data-lake-testing", "getMore", "A successful find event with getMore");
      • def.skipNoncompliant("The driver doesn't reduce the batchSize for the getMore")
        .test("unified-test-format/tests/valid-pass", "poc-command-monitoring",
        "A successful find event with a getmore and the server kills the cursor (<= 4.4)");

      In these cases the batchsize sent is larger than expected.

      DRIVERS-1447 & DRIVERS-3009 clarify the expected behaviour if limit == batchSize. However, when limit > batchSize our driver behaviour is different than expected.

            Assignee:
            Unassigned
            Reporter:
            Ross Lawley
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: