Here's a branch to address the original report, as well as the followup issue with cstore exhaustion. From the commit message:
If a nullable event grouping field is configured, and a null value is indeed encountered when pulling together events, the Action/Trigger code will exit unceremoniously. To prevent this, we will now collect events with either a null grouping object or grouping field, and use a new batch invalidation API call to get rid of them as quickly as possible after group sorting is complete.
Here's a branch to address the original report, as well as the followup issue with cstore exhaustion. From the commit message:
If a nullable event grouping field is configured, and a null value is indeed encountered when pulling together events, the Action/Trigger code will exit unceremoniously. To prevent this, we will now collect events with either a null grouping object or grouping field, and use a new batch invalidation API call to get rid of them as quickly as possible after group sorting is complete.
http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=commitdif f;h=b3f7dd8557b c53a31bf097e927 95e28b6a92fa1f