Project

General

Profile

Actions
Copy link

Bug #4442

open

Spatial indexing should not run and block metacat

Added by Michael Daigle over 14 years ago. Updated almost 11 years ago.

Status:
New
Priority:
Normal
Assignee:
ben leinfelder
Category:
metacat
Target version:
2.x.y
Start date:
10/07/2009
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
4442

Description

spatial indexing runs after a fresh install the first time someone accesses metacat servlet. It blocks any calls until it is done. This can take over thirty minutes in production knb.

It should run it the background, and possibly be kicked off by a scheduler.

Related issues

Related to Metacat - Feature #5810: Implement SOLR-based searchClosedJing Tao01/24/2013

Actions
Actions
Copy link
 #1

Updated by Michael Daigle over 14 years ago

moving to 1.9.3 target

Actions
Copy link
 #2

Updated by Matt Jones over 12 years ago

Related to bug #3811.

Actions
Copy link
 #3

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 4442

Actions
Copy link
 #4

Updated by ben leinfelder about 11 years ago

  • Assignee changed from Michael Daigle to ben leinfelder
  • Target version changed from Postpone to 2.1.0

Thoughts:
-if it runs in the background it is entirely possible to get incomplete results if you query as the index is being [re]built.
-we should consider how this search API can be replaced by the SOLR implementation. Showing the point/bounding boxes is a cool feature and one that we don't necessarily get with the coordinates being indexed in SOLR, but it seems like the spatial cache could easily be populated from the SOLR index and that would not block Metacat start-up because indexing will be running essentially stand-alone.

Actions
Copy link
 #5

Updated by ben leinfelder almost 11 years ago

  • Target version changed from 2.1.0 to 2.x.y
Actions
Copy link

Also available in: Atom PDF