Project

General

Profile

Task #2069

Story #2067: Refactor the index task generator and processor to improve scalability and performance

Select a persistence technology for the index task queue

Added by Dave Vieglais about 13 years ago. Updated about 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Skye Roseboom
Category:
d1_indexer
Start date:
2011-11-29
Due date:
% Done:

100%

Milestone:
CCI-1.0.0
Product Version:
*
Story Points:
Sprint:

Description

Spring Data (http://www.springsource.org/spring-data) seems like a good choice, perhaps with the JPA or JDBC connection. Postgres is installed on the CNs for use by Metacat, would make sense to use this for the persistence mechanism, though need to check on resource use by Metacat to ensure there are sufficient connections available for the indexer to operate.

History

#1 Updated by Skye Roseboom about 13 years ago

  • Status changed from New to Closed

Implemented JPA using Hibernate with Spring configuration. Spring Data is providing a JPA Repository so no need to write a DAO.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)