4

I just started integrating Hibernate Search with my Hibernate application. The data is indexed by using Hibernate Session every time I start the server. 

FullTextSession fullTextSession = Search.getFullTextSession(session);
Transaction tx = fullTextSession.beginTransaction();

List books = session.createQuery("from Book as book").list();
for (Book book : books) {
    fullTextSession.index(book);
}

tx.commit(); //index is written at commit time

It is very awkward and the server takes 10 minutes to start. Am I doing the this in right way?

I wrote a scheduler which will update the indexes periodically. Will this update the existing index entries automatically, or create duplicate indices?

Improve this question

3 Answers 3

Reset to default
10

As detailed in the Hibernate Search guide, section 3.6.1, if you are using annotations (by now the default), the listeners which launch indexing on store are registered by default:

Hibernate Search is enabled out of the box when using Hibernate Annotations or Hibernate EntityManager. If, for some reason you need to disable it, set hibernate.search.autoregister_listeners to false.

An example on how to turn them on by hand: 

 hibConfiguration.setListener("post-update", new FullTextIndexEventListener());
 hibConfiguration.setListener("post-insert", new FullTextIndexEventListener());
 hibConfiguration.setListener("post-delete", new FullTextIndexEventListener());

All you need to do is annotate the entities which you want to be indexed with the 

@Indexed(index = "fulltext")

annotation, and then do the fine-grained annotation on the fields, as detailed in the user guide.

So you should neither launch indexing by hand when storing, neither relaunch indexing whae the application starts, unless you have entities which have been stored before indexing was enabled.

You may get performance problems when you are storing an object which say has an "attachment" and so you are indexing that in the same scope of the transaction which is storing the entity. See here:

Hibernate Search and offline text extraction

for a solution that solves this problem.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

This answer in particular shows that was has been accepted as answer above is WRONG. You should NOT as a general procedure launch indexing by hand when storing an entity.
1

Provided you are using a FSDirectoryProvider (which is the default) the Lucene index is persisted on disk. This means there is no need to index on very startup. If you have existing database you want of course to create an initial index using the fullTextSession.index() functionality. However, this should not be on application startup. Consider exposing some sort of trigger url, or admin interface. Once you have the initial index I would recommend to use automatic indexing. This means that the Lucene index gets automatically updated if a books get created/updated/deleted. Automatic indexing should also be enabled by default.

I recommend you refer to the automatic and manual indexing sections in the online manual - http://docs.jboss.org/hibernate/stable/search/reference/en/html_single

--Hardy

Improve this answer

2 Comments

How can Automatic indexing be enabled? What is the configuration for the same?
If you are using Hibernate Annotations automatic indexing will be enabled by default. If you are not using Annotation you have to register the FullTextIndexEventListener: docs.jboss.org/hibernate/stable/search/reference/en/html_single/…
0

I currently use Hibernate Search's automatic indexing with JPA and it works really well. To create your indexes initially you can just call the following:

    FullTextEntityManager fullTextEntityManager = 
                    Search.getFullTextEntityManager(entityManager);

    try {
       fullTextEntityManager.createIndexer().startAndWait();
    } catch (InterruptedException e) {
       // Exception handling
    }

where "entityManager" is just a javax.persistence.EntityManager. The above will index all fields marked with @Field for all entities marked as @Indexed.

Then as long as you do all your updates, etc, through the entity manager the indexes are automatically updated. You can then search as per usual but be sure to recreate your EntityManager on each search (you can use the EntityManagerFactory to do so).

Improve this answer

3 Comments

Note that this is only available with Hibernate Search version 3.2+ (see Hibernate Search 3.2: fast index rebuild
@KyelJmD yes. The application that I work on that uses this is single DB multi-tenant. Or are you referring to multi-DB / multi-schema multi-tenant? Then I am not sure, you would have to try it out.
@brent777 I was referring to a multi-schema multi-tenant. I already ran this piece of but it didn't work.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.