Re: [uportal-dev] EventHandler implementation that prunes older events from the DB periodically?

[Eric Dalquist]

Why does it need to be an EventHandler? How about a simple bean that is called via the scheduler periodically? It along with the assocated trigger could still be declared and configured in the statsContext.xml but it seems strange to overload EventHandler for a purpose that isn't actually handling any events.

-Eric

On 07/06/2010 12:28 PM, Drew Wills wrote:

Also anecdotally we've found that doing small purges more often is much easier on the stats database than once per day. Perhaps have this thing purge events older than X days and have run once per hour?

Hey folks,



  - ignores all events, except 1 event every xyz period (probably a day)




drew wills

Is there general interest in a concrete EventHandler class that does something like the following: - on that event, runs a DB update to scrub events older than abc (maybe a month) - optionally (re)writes those events to some other form of storage, like a file or perhaps a separate, archival DB? I'm thinking of this service as an EventHandler impl so it can be configured and managed part-and-parcel with everything else in statsContext.xml.

smime.p7s
Description: S/MIME Cryptographic Signature