Project

General

Profile

Bug #6424

Obsoleted objects not marked in index

Added by ben leinfelder over 5 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Category:
index
Target version:
Start date:
02/25/2014
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

Looks like between 2.3.1 and 2.4.0 a lot of indexing code was commented out or removed and I believe some of it was to update indexed documents when newer versions are added.
I don't see anything that will update the solr index for the objected identified by an entry in SM.obsoletes. So we end up with two versions of the same objects in the index (and the UI).

History

#1 Updated by ben leinfelder over 5 years ago

  • Status changed from New to In Progress

When we decided to keep obsoleted objects in the index, we neglected to update their entries in the index when they were obsoleted by newer objects -- only adding the new objects to the index and leaving the older ones the same.

I added handling in Metacat to submit the obsoleted object pids (recursively) when the newest version is added -- this ensures we keep the index up-to-date for the entire chain whenever it is modified, though it might be overkill in some instances.

#2 Updated by ben leinfelder over 5 years ago

  • Status changed from In Progress to Closed

Now re-indexing the obsoleted revision[s] of any new objects that are added with update commands. Note that we do not recurse when doing things like "reindexall" as this process already does every pid (including revisions).

Also available in: Atom PDF