Grouper Users - Open Discussion List

[Scott Koranda <>]

Hi,

On Thu, Apr 17, 2014 at 10:03 AM, Chris Hyzer 
<>
 wrote:
> Deep in the api, the only way to create a group is by specifying the
> extension and display extension, then if you want to add a description, you
> can update the group.  I think in the loader this happens with one groupsave
> call which does the insert and update in one transaction.

I think I see this, yes. I don't have time today to trace through all
the code but I think I see how the loader job eventually invokes the
syncOneGroupMembership() method with the information from the SQL
query, and in that call I see the invocation of the save() method on
the GroupSave object. The save() method appears to use the description
if present and it is all wrapped in one transaction.

Thanks.

> This means it's
> impossible for a change log consumer to not get the description.

It looks that way, yes, and I can easily test and log if that does not happen.

> But yes,
> if this isn't ok, and we want the description to not get another change log
> event, I could do that.  Chris

I think it would be a low priority given how it currently works. I
suppose it would be cleaner for people implementing change log
consumers in that they can take the one addGroup event and get the
name and description without having to use the API to query or "wait"
for the updateGroup event.

I will create a JIRA so it is there.

Thanks again,

Scott K


>
>
> -------- Original message --------
> From: Scott Koranda 
> <>
> Date: 04/17/2014 10:46 AM (GMT-05:00)
> To: Chris Hyzer 
> <>
> Cc: grouper-users 
> <>
> Subject: Re: RE: [grouper-users] SQL loader jobs, change log consumer and
> obtaining group description
>
>
> On Thu, Apr 17, 2014 at 9:42 AM, Chris Hyzer 
> <>
>  wrote:
>> 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.
>
> Ok, thanks.
>
>>If you want me too fix that please open a jira and assign to me
>
> Do you mean "fix" that the group description does not appear in the
> addGroup change log event? Is that what you are willing to consider?
>
> Cheers,
>
> Scott
>
>>
>> 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