Subject: Grouper Users - Open Discussion List
- From: Michael Gettes <>
- To: Chris Hyzer <>
- Cc: " Mailing List" <>
- Subject: Re: [grouper-users] "cursor" based paging
- Date: Thu, 5 Dec 2019 09:04:08 -0500
Of the 4 below - number 4 seems like it could be most interesting if that results in consistent behavior even for normal/small groups vs. large groups. Opening a large group which hasn’t been cached yet can take a long time so 2 could also be there. If I read between the lines - number 4 would be able to page use of the paged queries of a membership??? Get the 1-75, then 76-150 and so on? That would be terrific.
On Dec 4, 2019, at 1:46 PM, Hyzer, Chris <> wrote:[External Email]It wouldn’t affect that speed but we should fix that.Its slow because:
- The query (shouldn’t be too slow)
- -or- Resolving all of the subjects (maybe we need caching changes? Maybe we need more things in member table to display subjects without resolving?)
- -or- Maybe not display members by default of large groups because who cares to look at first page of 500k group? Maybe display immediate only if there are only a few groups in the group?
- -or- Maybe display the page and get the member list in ajax so you don’t have to wait for it?From: Gettes, Michael <>
Sent: Wednesday, December 04, 2019 11:17 AM
To: Hyzer, Chris <>
Cc: Mailing List <>
Subject: Re: [grouper-users] "cursor" based pagingWill this paging be implemented for the UI so opening a 500K member group in the UI could be instantaneous?/mrgOn Dec 1, 2019, at 10:16 PM, Hyzer, Chris <> wrote:[External Email]
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? 😊Thanks!Chris
Description: S/MIME cryptographic signature
- [grouper-users] "cursor" based paging, Hyzer, Chris, 12/02/2019
Archive powered by MHonArc 2.6.19.