[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-781?pag...
]
Sanne Grinovero commented on HSEARCH-781:
-----------------------------------------
Interesting idea.
I didn't look at the API differences, but it should be doable - however it is my
understanding that it's not maintained anymore, so I wonder if it would make sense.
As an alternative we could re-implement something similar to maintain it properly but
I've always been skeptical about how good it fits in a database, especially
performancewise: I might be wrong but it doesn't feel like the right tool for the
job.
Did you consider using the Infinispan Lucene Directory instead? It would cache as much as
possible in memory, but you can still enable a cachestore to persist the index in a
database so that you can always kill the nodes without losing the index. This is how I use
it myself most of the time, but it takes some configuration files. I guess we could
simplify the configuration of it or at least provide more examples.
Add a database backed Directory and DirectoryProvider
-----------------------------------------------------
Key: HSEARCH-781
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-781
Project: Hibernate Search
Issue Type: New Feature
Components: directory provider
Affects Versions: 3.4.0.Final
Reporter: Ted Pennings
It would be great if there were a database backed Luncene Directory and
DirectoryProvider. This would be roughly similar to what Compass provided with their
JdbcDirectory class. Unfortunately due to Lucene API differences, it's not easy to
drop the Compass JdbcDirectory into Hibernate Search.
--
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