Hi Emmanuel!
> Remember that while you can use the same index for your whole domain
> model, One index per entity is the recommended approach. Do you expect
> a finer grained model? Under which partition strategy?
First, I hadn't had the time till now to have a look at Hibernate
Search, so sorry if
Remember that while you can use the same index for your whole domain
model, One index per entity is the recommended approach. Do you expect a
finer grained model? Under which partition strategy?
Mario Ivankovits wrote:
Hi Emmanuel!
> 2. add an FullTextSession.optimize(Class) method, and the a
Hi Emmanuel!
> 2. add an FullTextSession.optimize(Class) method, and the application
> is responsible for the method trigger. This is the easy solution but
> put more work on the user. And I'm not happy to push a maintenance API
> to the Session. Esp since this is more of a SessionFactory like API.
The problem is not solved "automatically" yet. But here is the reason why.
First of all, the elements are properly deleted, and the index file
reflect that as soon as IndexReader.close() is called (which is done by
Hibernate Search). However, the files containing the document data are
not clean
Hi,
I found the cool new feature of hibernate search in Lucene-user mail list by
Emmanuel's mail.
u guys did a very greate job! Since i am now working on a system that using
lucene to implement a search engine, i would like to know some more
details about Hinbernate Search.
I have read some o
