Skip to Content.
Sympa Menu

grouper-users - [grouper-users] "cursor" based paging

Subject: Grouper Users - Open Discussion List

List archive

[grouper-users] "cursor" based paging

Chronological Thread 
  • From: "Hyzer, Chris" <>
  • To: " Mailing List" <>
  • Subject: [grouper-users] "cursor" based paging
  • Date: Mon, 2 Dec 2019 03:16:49 +0000
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EcRULBrGI409FIDxOGHxmAy/YxVCW1VsWSb4lwkvqK0=; b=J8j5rj6r/k49TIIHb3fhnC6HBFAn7K6gdhP6HqTYiL4iEIOKF7sATEsmAIqk+FxdsSrOjo5n33yRNgmtIKTvn7ni84MPc2xnhIasxD8QjrMgAJgDdBLtdprvI+eltb/Fvqiea0OT92IzoO459arSiOwXO9jk6uR/qe+Kn/TvYYYAFzLLf0sqTYJotCC6yKc7bo9bWE+8nJlHAoUYLd3Z0e8LMEh3VDaTaqpT51MGp2WAEmVVU2wCe3Sn3V9VMCtFNaycbO0900Q5hnhqeU8yNLBILPRITgkJOxqd3/DPvAKbqaCCnIuGq4HtRvsAmIDKXpv5MQr6uPTzGO1gtiqHfQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=g8V/8Ig8NpmWhRrVygKI3pdjrTzgxPcuA3685HCbkUcv2xifz/mYwgo/oDAYErOBPBc8Yiny3Uaw1qkZLnac+MjBac9K7q5jvqMUiQrWwekIfr62XrU6jqMa4WDVpVO4Q5ezlDC0yFqcRIBQZWCZkG0H+y4is0ND7joSpmBc9WUWToqrupPub6l4hY0varu/VolMyNG8Q/IFQuK1V90o7D3vASrg4tV9lk38Yc8HiUXVLXveBmb23GTNui9LtDW1ItQNGDfWJM2h++RjMmUBmGjThi6Tl2NZHc5UzXLKZoItzQ+UAKfmYTbu0yAx84Sbrgf5K9JeFuIqVNf/y+oigA==

The paging in Grouper has been about pageSize and pageNumber and cycling through records.


If you page through a large dataset, if the records change while you are paging through, you can get inconsistent results.


However, if pass in the last id (or whatever you are sorting on), and ask for a page starting after that record (what we are calling “cursor-paging”), then you will not miss records as they change while the paging is occurring.  Note, no database or memory actual cursors are being used here.


This has been implemented in the 2.5 branch and will be in the WS in 2.5.


Does that make sense?  Anyone interested in a particular use case?


For our box implementation we download the box users with netIDs.  Which is getting 70k subjects and resolving them I believe.  The WS call times out sometimes so maybe we should do something like this.  Other ideas?  😊





Archive powered by MHonArc 2.6.19.

Top of Page