Grouper Users - Open Discussion List

["Waldbieser, Carl" <>]

Chris,

I meant, "is there an easy way to translate the UUIDs into something that 
makes sense to me?"  So I can look at something like:

  
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
 "5ec8735b43f546d08061ca33a73a4964", "612e954d58c44e37985e4e6fbb0f3b9a"));

And translate it into something like: "This will add subject 'waldbiec' to 
group 'network-overlords'."
I'm not looking for something that translates into human language-- just 
something to spit out what the proposed action is, and translate the group 
and subject names if possible.

Thanks,
Carl

----- Original Message -----
From: "Hyzer, Chris" 
<>
To: "waldbiec" 
<>,
 "Kumi Hagimoto" 
<>
Cc: 

Sent: Tuesday, October 18, 2016 12:37:17 PM
Subject: RE: Composite with complement did not update?

There is no bad-badmembershipfinder-finder... that is the correct script.  
And note, you should run it again afterwards until it says things are good.

Note, 2.3 api patch 23: find bad memberships daemon

https://spaces.internet2.edu/display/Grouper/v2.3+Release+Notes
https://bugs.internet2.edu/jira/browse/GRP-1367

This will run automatically so you don’t need to worry about it.

Thanks
Chris

-----Original Message-----
From: 

 
[mailto:]
 On Behalf Of Waldbieser, Carl
Sent: Tuesday, October 18, 2016 12:28 PM
To: Kumi Hagimoto 
<>
Cc: 

Subject: Re: [grouper-users] Composite with complement did not update?

Kumi,

That does look to be what happened.
When I run the bad membership finder, I get an output script with a number of 
statements that I'm not sure what they are doing:

    GrouperSession.startRootSession();
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
 "5ec8735b43f546d08061ca33a73a4964", "612e954d58c44e37985e4e6fbb0f3b9a"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
 "892bc28297f94372a5179eeec548c63e", "612e954d58c44e37985e4e6fbb0f3b9a"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
 "9aa9723ce7df4025a68c91d9450c6371", "0c354eb1eef74201a383b515d8b456bb"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
 "faf83a9bac5e4832adc38ab64f4e6427", "0c354eb1eef74201a383b515d8b456bb"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
 "faf83a9bac5e4832adc38ab64f4e6427", "612e954d58c44e37985e4e6fbb0f3b9a"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("71f7aba21f3948399727c4ec33fd3c1e",
 "fdaf8e85ee264f3eb83be6ced20276f1", "0c354eb1eef74201a383b515d8b456bb"));
    
GrouperDAOFactory.getFactory().getMembership().save(Composite.internal_createNewCompositeMembershipObject("63f2036200ff48d48aa463e33ca43622",
 "fdaf8e85ee264f3eb83be6ced20276f1", "612e954d58c44e37985e4e6fbb0f3b9a"));
    sqlRun("delete from grouper_memberships where 
id='7a2e3a0e7365426a9b2c73602b3f99c2'");
    sqlRun("delete from grouper_memberships where 
id='d3f6b104d5ab4a959e62dbec06d46a46'");

The last 2 seem to be removing some obsolete groups.
Are the `Composite.internal_createNewCompositeMembershipObject` creating 
missing memberships?  Is there some way to (easily) check these before 
updating?

Thanks,
Carl

----- Original Message -----
From: "Kumi Hagimoto" 
<>
To: 
,
 "waldbiec" 
<>
Sent: Tuesday, October 18, 2016 11:58:47 AM
Subject: Re: [grouper-users] Composite with complement did not update?

Hi Carl,

Looks like maybe you're seeing the same issue we have with v2.2.1?

https://lists.internet2.edu/sympa/arc/grouper-users/2016-09/msg00033.html

We just run the BadMembership gsh generated by nightly report until we
upgrade.

Thanks,
Kumi