Page History

Prior to 4.11.0, Grouper would make composite membership adjustments whenever a change was made to the composite or its factors. For groups that were factors in many composites(e.g. reference groups), a membership change could result in many composite adjustments and have a considerable performance impact.

Starting with 4.11.0, the job CHANGE_LOG_consumer_findBadMemberships was renamed to CHANGE_LOG_consumer_compositeMemberships and handles these adjustments with improvements in batch lookups and multiple threads.  This long-running job checks, makes changes, and sleeps for 500ms before checking again. 

This change may create a different user experience for end users familiar with prior versions and proper communication about the change is recommended.

 For adding and removing direct members, there would be is an exception (based on regex of group names) to allow for the old behavior (having the composite calculations done in the same transaction) .using composites.synchronousCalculationGroupNameRegex in grouper.properties.