⁠Chapter 8. Manual Index Changes

8.1. Adding Instances to the Index
8.2. Deleting Instances from the Index
8.3. Rebuilding the Index
8.3.1. Using flushToIndexes()
8.3.2. Using a MassIndexer
As Hibernate core applies changes to the Database, Hibernate Search detects these changes and will update the index automatically (unless the EventListeners are disabled). Sometimes changes are made to the database without using Hibernate, as when backup is restored or your data is otherwise affected; for these cases Hibernate Search exposes the Manual Index APIs to explicitly update or remove a single entity from the index, or rebuild the index for the whole database, or remove all references to a specific type.
All these methods affect the Lucene Index only, no changes are applied to the Database.
Report a bug

⁠8.1. Adding Instances to the Index

Using FullTextSession.index(T entity) you can directly add or update a specific object instance to the index. If this entity was already indexed, then the index will be updated. Changes to the index are only applied at transaction commit.
⁠

Example 8.1. Indexing an entity via FullTextSession.index(T entity)

​FullTextSession fullTextSession = Search.getFullTextSession(session);
​Transaction tx = fullTextSession.beginTransaction();
​Object customer = fullTextSession.load( Customer.class, 8 );
​fullTextSession.index(customer);
​tx.commit(); //index only updated at commit time
In case you want to add all instances for a type, or for all indexed types, the recommended approach is to use a MassIndexer: see Section 8.3.2, “Using a MassIndexer” for more details.
Report a bug