[hibernate-issues] [Hibernate-JIRA] Updated: (HSEARCH-758) Have DirectoryManager handle different I/O aspects of an index
Sanne Grinovero (JIRA)
noreply at atlassian.com
Wed Aug 17 11:32:02 EDT 2011
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero updated HSEARCH-758:
------------------------------------
Fix Version/s: (was: 4.0.0.Alpha1)
4.0.0.Alpha2
> Have DirectoryManager handle different I/O aspects of an index
> --------------------------------------------------------------
>
> Key: HSEARCH-758
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-758
> Project: Hibernate Search
> Issue Type: Improvement
> Reporter: Sanne Grinovero
> Assignee: Sanne Grinovero
> Fix For: 4.0.0.Alpha2
>
>
> Near-Real-Time Lucene usage requires a coupling between the indexwriter and the indexreaders being used for searches.
> Also to make other features simpler we need to manage indexwriters and indexreaders in a more integrated form (Infinispan).
> refactor : DirectoryProvider
> * make a "DirectoryManager" instead, which is able to provide factories for both IndexReader an IndexWriters
> * add utility methods like "getName()"
> o (wish I had that in some cases to provide better error messages)
> * Instead of trying to foresee all needed methods, the extension point should not be the DirectoryManager interface directly, but have people plug in different aspects.
> * This is needed to eventually support:
> o Instantiated indexes - HSEARCH-336
> o make good use of all new so called "Near-Real-Time" Lucene improvements by having IndexReader and IndexWriter possibly generated by the same service
> o reuse the JGroups channel used by the Infinispan Directory as transport for a backend (again, the two components need to interact)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list