The Hibernate Search - JSR-352 integration provides a mass indexing batch processing job for use with JSR-352 runtimes. Essentially it replaces the MassIndexer and adds a few interesting feature like stop/resume and resume after failure.

Currently it's known to work with JBatch (the reference implementation) and JBeret (the WildFly implementation). It is known not to work with Spring Batch: HSEARCH-2692 Open .

The integration does not work with OGM for now because it relies on criteria and org.hibernate.query.Query#scroll(org.hibernate.ScrollMode), which are not supported in OGM yet.

When OGM supports those, we might want to have a look to see if everything works as expected. In particular there's a bit of hacking involved in the JSR-352 integration to retrieve the session, which might not work perfectly well with OGM.

Examples of tests can be found in Hibernate Search:

• For Java SE: https://github.com/hibernate/hibernate-search/blob/master/integrationtest/jsr352/src/test/java/org/hibernate/search/jsr352/massindexing/RestartChunkIT.java
• For WildFly: https://github.com/hibernate/hibernate-search/blob/master/integrationtest/wildfly/src/test/java/org/hibernate/search/test/integration/jsr352/massindexing/RestartIT.java

Note that tests require additional configuration. In particular, the Java SE tests requires to set up JBatch (have a look at the POM and resource files). You should probably avoid JBeret SE as all of its dependencies have the "provided" scope, which is a nightmare.