Repository navigation
[bug] updateMany does not proceed past first page #106
Description
When updateMany requires multiple requests, the "nextPageState" is read incorrectly from the first response and is always seen as null, thereby preventing any subsequent page from being properly processed.
As a result, only up to 50 (formerly 20) items get updated.
Root cause: the next page state is read from data rather than from status (where it is located).
This happens here in the updateMany collection method:
if (res.getData() != null) {
nextPageState = res.getData().getNextPageState();
}
Reference response from a more-than-50-items updateMany HTTP request:
{
"status": {
"documentResponses": null,
"sortVector": null,
"warnings": null,
"primaryKeySchema": null,
"projectionSchema": null,
"insertedIds": null,
"moreData": true,
"modifiedCount": 50,
"matchedCount": 50,
"nextPageState": "LQAAAAEBAAAAJDM3MGEwNzZkLTdiMzQtNDMxYS04YTA3LTZkN2IzNDAzMWE1MQDwf///zQA="
},
"data": null,
"errors": null
}
Activity
fix: updateMany does not proceed past first page (#106) (#107)
sl-at-ibm commentedon Sep 17, 2026
Closed by #107