Hibernate Search version
5.4.0.CR1 is now available! It was built and tested with Hibernate ORM
essentially it’s all ready for ORM 5 and we’ll just be waiting for this to be marked
<dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-search-orm</artifactId> <version>5.4.0.CR1</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-core</artifactId> <version>5.0.0.CR2</version> </dependency> <dependency> <groupId>org.hibernate</groupId> <artifactId>hibernate-entitymanager</artifactId> <version>5.0.0.CR2</version> </dependency>
You can now have the
MassIndexer set a different timeout for the internal transactions it will start,
so if you’re running Hibernate Search in a container like WildFly you no longer have to make a choice
between having a deadline of 5 minutes or changing the default timeout of the whole container.
fullTextSession .createIndexer( User.class ) .transactionTimeout( 1800 ) //seconds .startAndWait();
As explained in more detail in last week’s post, Hibernate Search now provides an option to include its indexing operations within the same transaction as the RDBMS.
In short, it’s enabled by setting this property:
But keep in mind: it’s a global setting! If you want to use it, all your backends shall be set to use an XA enabled, transactional JMS queue.
Please let us know if you have a great use case which would require us to allow some form of mixed mode.
The first WildFly version to use Hibernate ORM 5 is version
which was released the past weekend.
So the JBoss Modules we create for this appserver are targeting now WildFly 10,
but at least version