Hi,

If I want to override \ extend the default behavior of Hibernate Search

Is there a way to get & use the IndexWriter that Hibernate Search uses?
Are there any interceptors \ hooks for the update \ delete operations?

Thanks,
Arik

Which behavior in particular do you want to override? There are several things you
can configure and/or provide custom implementations for.


There is no way to get hold of the IndexWriter. Potentially you could implement a custom
BackendQueueProcessor, but it all depends on what you want to do.

Can you provide some more details about your usecase?

--Hardy

Hi Hardy!

Thanks for the quick response!
In our system, we need to have multiple index records for single object.
Hence I want to index the same object twice.

I actually extended the LuceneBackendQueueProcessor, and added additional lucene works.

It solved my problem.

Now I have other issue that the IndexWriter that I fetch from the LuceneBackendQueueProcessor remains locked...

should I close the writer when finished using it? (shouldn't it remain open for next uses?)

Hi,
the IndexWriter lifecycle depends on configuration. Closing one and re-opening for each update work is expensive in terms of performance and lots of disk I/O, so the default is to keep it open, and only flush changes at the end of each transaction.

See exclusive_index_use at http://docs.jboss.org/hibernate/search/4.0/reference/en-US/html_single/#table-performance-parameters