Bug #2141
closed
resultset cache expiration problem
Added by Chad Berkley almost 19 years ago.
Updated about 18 years ago.
Description
The cache needs to be fixed so that resultsets expire and are purged according
to a set policy. This was discussed at the 05 june kepler meeting. efrat and
jing agreed to fix it.
This has still not been resolved. Reassigning to kruland. Cache expiration
policies should be settable for each type of cache object, including the option
to mark some items as non-purgable. Resultsets from queries (e.g., in DiGIR)
should probably be handled differently than immutable objects (ie, LSID
identified actors, data, EML docs).
In CVS, CacheExpiration can now be set on each CacheObject. There are three
different expiration "policies", by date, never, and after session. The cache
contents is expired (including session objects) when the CacheManager's
singleton instance is created. I have set the QueryAction to have "Session"
expiration. The contents of the Quick Search will be "flushed" with kepler restart.
Original Bugzilla ID was 2141
Also available in: Atom
PDF