[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-135) Create a RAMDirectoryProvider from an existing Lucene FSDirectory
[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-135?pag...
]
Emmanuel Bernard commented on HSEARCH-135:
------------------------------------------
What is the benefit of not using a RAMDirectory wrapper when writing the index?
Also there is a problem, once your index is loaded in memory, what happens if another
process update it: I bet it's not reloaded (BTW you have the same problem when you
want the ro directory in RAM and the rw on file).
I'd rather avoid having 2 methods to access a directory, these are directly exposed to
the user.
Create a RAMDirectoryProvider from an existing Lucene FSDirectory
-----------------------------------------------------------------
Key: HSEARCH-135
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-135
Project: Hibernate Search
Issue Type: New Feature
Components: directory provider
Reporter: Hardy Ferentschik
It would be nice to have the ability to use a Lucene RAM index which gets constucted from
an existing Lucene file based indexed. For example in an JMS setup the master could create
a file based Lucene index, share it out to the slaves which in turn use this file based
index to populate a RAM index. This would give you the best of two worlds.
Not sure how hard it would be to implement this in an unclustered environment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see: http://www.atlassian.com/software/jira