Project

General

Profile

Bug #2141

resultset cache expiration problem

Added by Chad Berkley over 14 years ago. Updated almost 14 years ago.

Status:
Resolved
Priority:
Immediate
Assignee:
Category:
data access
Target version:
Start date:
07/05/2005
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
2141

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.


Related issues

Blocked by Kepler - Bug #2133: Need ability to update data searchesNew06/23/2005

History

#1 Updated by Matt Jones about 14 years ago

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).

#2 Updated by Kevin Ruland almost 14 years ago

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.

#3 Updated by Redmine Admin over 6 years ago

Original Bugzilla ID was 2141

Also available in: Atom PDF