Skip to Content.
Sympa Menu

grouper-users - RE: [grouper-users] SQL loader jobs, change log consumer and obtaining group description

Subject: Grouper Users - Open Discussion List

List archive

RE: [grouper-users] SQL loader jobs, change log consumer and obtaining group description


Chronological Thread 
  • From: Chris Hyzer <>
  • To: Scott Koranda <>, grouper-users <>
  • Subject: RE: [grouper-users] SQL loader jobs, change log consumer and obtaining group description
  • Date: Thu, 17 Apr 2014 10:42:18 -0400
  • Importance: normal

Seems like it's not impossible for a race condition to occur, but the change log processing from temp occurs 10 seconds before change log consumers are executed, so I think that update would happen when you need it to almost always.  If you want me too fix that please open a jira and assign to me

Thanks
Chris



-------- Original message --------
From: Scott Koranda <>
Date: 04/17/2014 10:02 AM (GMT-05:00)
To: grouper-users <>
Subject: [grouper-users] SQL loader jobs, change log consumer and obtaining group description


Hello,

I am using Grouper 2.1.5.

When groups are created using an SQL loader job that has a
grouperLoaderGroupQuery defined that includes a column for the
GROUP_DESCRIPTION the change log has two distinct entries for each
loaded group:

1) an 'addGroup' event that includes, among other things, the group
name but that does not include the group description

2) an 'updateGroup' event that includes the group description

If a change log consumer were to take the addGroup event and do a
query using the Grouper API to get the group description is it
guaranteed to always find it? Or is it only reliable to obtain the
group description after receiving the updateGroup event? What if the
database/grouper is under heavy load? Is there any scenario where
querying for the group description after receiving the addGroup event
can fail under heavy load?

Thanks,

Scott K



Archive powered by MHonArc 2.6.16.

Top of Page