Project

General

Profile

Actions

Bug #5370

closed

AnnotationManager: persistence layer [re]initialization

Added by ben leinfelder almost 13 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
Normal
Category:
Metacat extensions
Target version:
Start date:
04/04/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5370

Description

When using the server-based persistence layer, Annotations that have previously been processed/imported will remain in the DB and can be immediately queried. The Metacat plugin, however, currently loops through every annotation document it finds during restart to load into this DB. We should add a configuration switch that is set in Metacat once the annotations have been imported so that it only happens once (and again when Metacat is upgraded/redeployed in the future, but not on every application restart). This is very similar to how the spatial cache works. Typically the annotations will be processed individually when they are inserted/updated/deleted (using the event handler).

Note: this will not work if we are using the in-memory Derby DB (like we would in Morpho and other smaller client-side deployments of the SMS library).

Actions

Also available in: Atom PDF