Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] JNDI Source and Paging

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] JNDI Source and Paging


Chronological Thread 
  • From: "James R. McCartney" <>
  • To: "Michael R. Gettes" <>
  • Cc: "" <>, Chris Hyzer <>
  • Subject: Re: [grouper-users] JNDI Source and Paging
  • Date: Tue, 21 Jul 2015 20:27:23 +0000
  • Accept-language: en-US

Okay, I'll keep that in mind.  I added the source with maxPageSize to the web ui and api, seems to work fine.

Thanks!
~james

From: "Michael R. Gettes" <>
Date: Tuesday, July 21, 2015 at 2:57 PM
To: James McCartney <>
Cc: "" <>, Chris Hyzer <>
Subject: Re: [grouper-users] JNDI Source and Paging

You’re making an interesting assumption about putting load on the directory.  It really depends on how your directory product works and exactly what problem you are trying to solve.  For example, most directory servers still have to fully resolve the query and then keep track of the query when handling paged searches.  There is a lot more back and forth with paged searches so it can actually be an increase in load.  if what you are wanting to do is to slurp up a search result of 50K then the server sends the data as fast as possible and the client eats as fast as it can.  Now, MS does 1000 pagesize by default - that doesn’t mean it’s a good thing.

if client and server are very close (network wise) then you may not want to do paged results for that client.

hope this helps.

/mrg

On Jul 21, 2015, at 15:49, Chris Hyzer <> wrote:

Try setting a maxPageSize for that adapter
 
    <init-param>
      <param-name>maxPageSize</param-name>
      <param-value>100</param-value>
    </init-param>
 
Note, you can still run an API call to search more widely, but I believe most of grouper runs paged queries so it will use that limit.  Someone can correct me if wrong J
 
Thanks,
Chris
 
 
 
From:  [] On Behalf Of James R. McCartney
Sent: Tuesday, July 21, 2015 11:24 AM
To: 
Subject: [grouper-users] JNDI Source and Paging
 
I have just installed grouper using the jar Installer and MySQL.  I have verified that all is working as expected.  My first step has been to remove the JDBC example source from the sources.xml file for subjects.  I am replacing it with a JNDI source to access my LDAP directory.  Since this directory as ~70000 entities, can I set a paging number to limit searches that would put a load on the directory?
 
 
What is the XML parameter syntax to limit searches or do paging in the sources.xml?  Thanks,
 
~james mccartney




Archive powered by MHonArc 2.6.16.

Top of Page