Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] Grouper 1.6.1 UI membership list sorting

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] Grouper 1.6.1 UI membership list sorting

Chronological Thread 
  • From: Peter DiCamillo <>
  • To: Chris Hyzer <>
  • Cc: "" <>
  • Subject: Re: [grouper-users] Grouper 1.6.1 UI membership list sorting
  • Date: Sun, 03 Oct 2010 02:40:41 -0400

I realize it doesn't scale, but that seems to be the purpose for comparator.sort.limit. I'd expect that if sorting is slowing things down too much I could lower the limit.

Sometimes I view the membership just to make sure it looks reasonable, without caring about the names of the individual people. But I think trying to determine if one or some specific set of members are in the list is common. Also, it's not always obvious that the list is not sorted, which can be very confusing I've seen cases where the names on the first page appeared to be sorted, but there were a few more names on the second page that would have sorted between names on the first page.

I don't have a workaround for 1.6. This didn't happen in for us in 1.3, and for 1.3 our person source was a database instead of LDAP. It looks like the solution we had for 1.3 was to include "order by" in the SQL defined for searches.


Chris Hyzer wrote:
I can reproduce that. The problem is that subject data is stored externally
to Grouper (in sources), so if there are 50000 subjects in a group, that is
50000 subject lookups (assuming none in cache), which doesn't scale. Granted
if you had 356 with 250 on a page, that should sort. :) What use case do
you have? Trying to see if someone is in a group? Just curious, what is the
workaround? Anyways, Im sure Gary will weigh in here as well...


-----Original Message-----

On Behalf Of Peter DiCamillo
Sent: Saturday, October 02, 2010 11:14 PM

Subject: [grouper-users] Grouper 1.6.1 UI membership list sorting

I'm having a problem where membership lists I view in the full Grouper UI are not sorted as I would expect. When the size of the membership list does not exceed the page size the list is sorted. But when more than one page is needed, the list on each page is not sorted. The value of comparator.sort.limit in is 50000, larger than the size of any of our groups, because even if it's slow, we always want sorted lists.

For example, I viewed a list with 2 direct members and 356 indirect members. When I viewed the indirect members or all members with a page size of 500 the list was sorted. But with a page size of 250 the lists on the pages were not sorted.

I didn't install Grouper 1.3, but we may have had a local fix for this. But in any case, it appears that since 1.3 the code that for handling pages and sorting has changed


Archive powered by MHonArc 2.6.16.

Top of Page