jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JCR-1747) org.apache.jackrabbit.core.query.lucene.SearchIndex with in-memory lucene index
Date Fri, 14 Nov 2008 13:30:44 GMT

     [ https://issues.apache.org/jira/browse/JCR-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Marcel Reutegger updated JCR-1747:

    Attachment: JCR-1747.patch

The attached patch introduces a DirectoryManager interface. There are two implementations

- FSDirectoryManager, this is the default, which matches the current behaviour
- RAMDirectoryManager, this one allows you to have an index that is completely held in memory

> 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
>         Attachments: 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.

View raw message