⁠8.2. Deleting Instances from the Index

It is equally possible to remove an entity or all entities of a given type from a Lucene index without the need to physically remove them from the database. This operation is named purging and is also done through the FullTextSession.
⁠

Example 8.2. Purging a specific instance of an entity from the index

​FullTextSession fullTextSession = Search.getFullTextSession(session);
​Transaction tx = fullTextSession.beginTransaction();
​for (Customer customer : customers) {
​    fullTextSession.purge( Customer.class, customer.getId() );
​}
​tx.commit(); //index is updated at commit time
Purging will remove the entity with the given id from the Lucene index but will not touch the database.
If you need to remove all entities of a given type, you can use the purgeAll method. This operation removes all entities of the type passed as a parameter as well as all its subtypes.
⁠

Example 8.3. Purging all instances of an entity from the index

​FullTextSession fullTextSession = Search.getFullTextSession(session);
​Transaction tx = fullTextSession.beginTransaction();
​fullTextSession.purgeAll( Customer.class );
​//optionally optimize the index
​//fullTextSession.getSearchFactory().optimize( Customer.class );
​tx.commit(); //index changes are applied at commit time
It is recommended to optimize the index after such an operation.

Note

Methods index, purge, and purgeAll are available on FullTextEntityManager as well.

Note

All manual indexing methods (index, purge, and purgeAll) only affect the index, not the database, nevertheless they are transactional and as such they won't be applied until the transaction is successfully committed, or you make use of flushToIndexes.
Report a bug