Grouper Users - Open Discussion List

[Chris Hyzer <>]

Vivek fixed this, its in a patch for 2.2.1. Try it out and let us know (note you need to configure it in the grouper-loader.properties.  I thought it should default as the current behavior, but if people disagree I can change the default so groups used in other groups are removed.  Let me know.

 

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

 

grouper_v2_2_1_api_patch_10

# if using a sql table, and specifying the name like string, then should the group be removed even when the group is member of some other group.

# loader.sqlTable.likeString.removeGroupIfNotUsed has to be true for this to work

# https://bugs.internet2.edu/jira/browse/GRP-1132

loader.sqlTable.likeString.removeGroupIfMemberOfAnotherGroup = false

 

 

Thanks,

Chris

 

 

From: Biernath, Jutta [mailto:]
Sent: Thursday, April 23, 2015 10:06 AM
To: Chris Hyzer;
Subject: AW: Loader Problem

 

The latter. It concerns all of our leaf nodes. When they are built they are automatically added as group members in the groups higher in the group hierarchy. It would be great if they could be deleted from there automatically as well.

 

Thanks,

 

Jutta

 

--------------------

Jutta Biernath

Freie Universität Berlin

Zentraleinrichtung für Datenverarbeitung (ZEDAT)

Identity & Customer Management, FUDIS

Fabeckstr. 32

14195 Berlin

Tel. +49 30 838-75090

Fax +49 30 838-475090

 

Von: Chris Hyzer []
Gesendet: Donnerstag, 23. April 2015 16:01
An: Biernath, Jutta;
Betreff: RE: Loader Problem

 

That logic is there because if someone is using a group, and it gets deleted, maybe there was a re-org or something and they need to see if they need to switch to another group.  Is this something you can review and manually delete, or are you asking for an enhancement where you can configure the loader to delete the group in this case?

 

Thanks,

Chris

 

From: [] On Behalf Of Biernath, Jutta
Sent: Thursday, April 23, 2015 9:42 AM
To:
Subject: [grouper-users] Loader Problem

 

Hi,

 

I have a problem with the “grouperLoaderGroupsLike” attribute of my loader jobs. The loader group is executed correctly and the groups to be deleted are also found. But if they are members of another group they are not deleted. The daily report is full of error messages like

 

subjobFor_XXXXXXX

status:            WARNING, started: 2015-04-23 14:05:32.065 (62ms)

ins/upd/del/tot:   0/0/0/0

error:             Not deleting group: XXXXXXX since used in 1 immediate memberships

 

All of these groups are empty but are members of other groups. I would expect that they are deleted nevertheless, as well as you can delete them in the UI although they are members anywhere else.

Now the database is full with groups that should have been deleted already. Usdu does not help, because the groups do still exist.

 

 

Thank you,

 

Jutta

 

 

--------------------

Jutta Biernath

Freie Universität Berlin

Zentraleinrichtung für Datenverarbeitung (ZEDAT)

Identity & Customer Management, FUDIS

Fabeckstr. 32

14195 Berlin

Tel. +49 30 838-75090

Fax +49 30 838-475090