implement alternative or improve repository metadata storage
------------------------------------------------------------
Key: MRM-1327
URL: http://jira.codehaus.org/browse/MRM-1327
Project: Archiva
Issue Type: Improvement
Components: system
Affects Versions: 1.4
Reporter: Brett Porter
The biggest thing to look at is metadata-repository-file. I threw this together
with property files quickly and there's no optimisation or even exception
handling. We need to look at the right way to approach this - a more robust
implementation of a file system store (properties or xml) is definitely
workable, but would need to be combined with something like a Lucene index (as
in Archiva 0.9) to make some of the operations fast enough. What I would like
to look at instead is using JCR (with file system persistence - not a
database!) to see how well it reacts to a lot of operations. As you can tell
from the docs, the storage is tailored to living in a hierarchical content
repository in whatever form that takes, and the storage is isolated behind an
API.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
