Long searches break event aggregation

[Jackson, Allan]

Are other people seeing this same bug we’re having issues with? The portal’s search field allows entering more than 255 characters, and this value gets saved in the up_raw_events table. Then when the event aggregation process runs, it can’t save the long value into the search aggregation table. This ends up blocking all event processing, and the raw events table just continues to grow until it’s millions of records and takes up many gigabytes of space.

 

https://github.com/Jasig/uPortal/issues/2160

 

Allan

[Benito Gonzalez]

Hi Allan,

This has come up a few times. Every time the client preferred to remove search events or even remove all events to reduce db contention.

Did you want us to add this to our Sustaining Engineering backlog or use some of your CA hours to address it?

--
You received this message because you are subscribed to the Google Groups "uPortal Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uportal-user...@apereo.org.
To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/uportal-user/540532C3-79A0-43BC-95C1-A33E7860E614%40ku.edu.