Grouper Developers Forum

[Shilen Patel <>]

On Mar 17, 2009, at 1:44 PM, Tom Zeller wrote:

Grouper Call 18-Feb-09**

[AI]  (TomZ) will confirm that Ldappc uses query filters to determine when a group was last modified. 

 

Last Membership Update Issue

Shilen:  Should we prevent updating the modifyUUID and modifyTime for a group or stem when a member or privilege is added or deleted and instead create last_membership_change attributes on groups and stems?

How would this affect Ldappc, which does membership updates based on the time the group was last updated?

TomZ will look into possible dependency with Ldappc: 

[AI]  (TomZ) will confirm that Ldappc uses query filters to determine when a group was last modified. 

Chris noted that, long-term, if Ldappc is moved to notifications, then we may not need the last_membership_change field at all. 

[AI] (Shilen) will create a Jira item for the UUID and last membership update issue. 

https://bugs.internet2.edu/jira/browse/GRP-228

Ldappc calls group.getModifyTime() to determine if a group has been modified recently. If the last time of a membership change is not available, then ldappc will have difficulty determining groups that need to be updated.

Perhaps we should make the last_membership_change attribute/column mandatory, and provide another method to return the last membership modification time, e.g. group.getMembershipModifyTime().

[I've added this comment to jira]

TomZ

 

Thanks TomZ.  I'll make the last_membership_change column mandatory then unless somebody has an alternate opinion.  Also, Chris added getLastMembershipChange() for both groups and stems.  I'm also going to be adding query filters for the new column.  So I think LDAP-PC can either use getLastMembershipChange() or the query filters (that will be added soon).

Thanks!

-- Shilen