Project

General

Profile

Task #173

Document mechanisms for interaction with Mercury system

Added by Dave Vieglais over 12 years ago. Updated about 12 years ago.

Status:
Closed
Priority:
High
Assignee:
Giri Palanisamy
Category:
d1_indexer
Target version:
Start date:
Due date:
% Done:

100%

Milestone:
None
Product Version:
*
Story Points:
Sprint:

Description

Mercury is to provide (simple fielded + full text) search capability with the goal of reducing the load on the document store (Metacat).

Documentation describing how the CN_service (i.e. the service implementing the outward facing CN APIs) might interact with the Mercury system is required. The general assumption made thus far is that the CN_Service will interact with the SOLR service or perhaps directly with the lucene index that Mercury is using.

Documentation (preferably) or relevant source is required to further define this aspect of implementation.

Basically:

  • how can the cn_service interact with Mercury?
  • how can the cn_service discover which fields are defined in the Marcury index?
  • What query formats are supported by the Mercury installation?
  • Which fields support enumeration (list unique values and their counts)?
  • Is faceting enabled?
  • What are the limits the the number of records returned in response to a single request?

History

#1 Updated by Dave Vieglais about 12 years ago

  • Status changed from New to Closed

Task to organize docs: #786

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)