You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/11/17 12:04:44 UTC
[jira] Resolved: (JCR-1747)
org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene
index
[ https://issues.apache.org/jira/browse/JCR-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger resolved JCR-1747.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Applied patch and added test case for DirectoryManager implementations.
svn revision: 718218
> org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene index
> -------------------------------------------------------------------------------
>
> Key: JCR-1747
> URL: https://issues.apache.org/jira/browse/JCR-1747
> Project: Jackrabbit
> Issue Type: Improvement
> Components: indexing, jackrabbit-core
> Affects Versions: 1.4
> Reporter: fabrizio giustina
> Priority: Minor
> Fix For: 1.6.0
>
> Attachments: JCR-1747.patch, JCR-1747.patch
>
>
> If I'm not wrong, there is actually no way to configure SearchIndex in order to use a memory only lucene index.
> Since you can configure a repository using a org.apache.jackrabbit.core.state.mem.InMemPersistenceManager, it makes sense that also search index offers a similar configuration.
> MultiIndex and PersistentIndex now always use a org.apache.lucene.store.FSDirectory, they should be refactored in order to allow a switching to a org.apache.lucene.store.RAMDirectory for this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.