Project

General

Profile

Actions

Bug #6123

closed

Rework on the IndexGenerator class in the metacat-index module

Added by Jing Tao about 11 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
10/04/2013
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

The IndexGenerator class has two purpose - first, to create the solr index for all data objects for a Metacat which is updated to use solr index; second, periodically to reindex those data objects which failed to be indexed during the insert/update.

Since the Metacat-index module can't directly access the information such as ids list, system metadata and et al (it use the hazelcast service) , the IndexGenerator is not very efficient and sometimes is problematic. So we may shift the task from this class to Metacat. Metacat decides when and which docids to be put into the index queue for indexing. Metacat-index module is just a listener.

Actions #1

Updated by ben leinfelder about 11 years ago

  • Target version changed from 2.2.1 to 2.3.0
Actions #2

Updated by Jing Tao about 11 years ago

I am thinking of the issues about moving the class to Metacat:

This class is a backup plan. If we move it to Metacat, so it still use a indirect way to index document. We don't add too much certainty.

Actions #3

Updated by ben leinfelder about 11 years ago

  • Target version changed from 2.3.0 to 2.4.0
Actions #4

Updated by ben leinfelder almost 11 years ago

  • Target version changed from 2.4.0 to 2.5.0
Actions #5

Updated by Jing Tao about 9 years ago

  • Status changed from New to Rejected
Actions

Also available in: Atom PDF