How do I paginate without overstating snapshot completeness? #76
|
What should a client do with next_cursor, next_offset, and provenance, and which parts of a cursor traversal remain live? |
Replies: 1 comment
|
For issue, event, issue-detail event, and history pages, follow Do not combine a cursor with a nonzero offset. Project and release lists use offset continuation only. MCP lists default to and cap at 20 entries; REST lists default to 50 and allow up to 100. Large MCP reads can reduce the effective page size, so inspect A cursor freezes event membership and ordering at the initial ingestion snapshot. Later inserts stay out, including inserts with backdated occurrence timestamps. Offset-only requests take fresh snapshots and can shift during ingestion. History cursors similarly freeze transition membership. This is not a frozen database copy. Issue status stays live, so a status-filtered traversal can change as statuses change. Issue Keep provenance with an exported result and state its project, filters, time scope, and snapshot limits. Check collected IDs for duplicates before claiming an exhaustive enumeration. See pagination semantics and MCP response limits. |
For issue, event, issue-detail event, and history pages, follow
next_cursoron the same endpoint and project with unchanged filters. Continue whilehas_moreindicates another page. A cursor page can havenext_offset: nulland still contain a continuation cursor; null means offset continuation is unavailable, not that the results are exhausted.Do not combine a cursor with a nonzero offset. Project and release lists use offset continuation only. MCP lists default to and cap at 20 entries; REST lists default to 50 and allow up to 100. Large MCP reads can reduce the effective page size, so inspect
effective_limitinstead of assuming each requested page will be full.A cursor freezes event me…