Tags
Authors
In the last couple of months we’ve been working to upgrade Hibernate Search to use Apache Lucene 5
,
to keep up with the greatest releases from the Lucene community.
Today Hibernate Search 5.5.0.Alpha1
is available!
As the version suggests this is the first cut, but we’ll also need your feedback and suggestions to better assess the needed steps to evolve this into a great, efficient and stable Final release.
While Hibernate ORM applies some more polish before releasing the final version, so did the Hibernate Search team.
Hibernate Search version 5.4.0.CR2
is now available!
It was built and tested with Hibernate ORM 5.0.0.CR3
, again we’re just waiting for that to be final but decided
to release another Candidate Release as some fixes and improvements were recently applied.
Writing queries using complex types can be a bit surprising in Hibernate Search. For these multi-fields types, the key is to target each individual field in the query. Let’s discuss how this works.
The Hibernate Search project roadmap was quite outdated, so after some team chats on IRC and our developer’s mailing list I’ve summarized our plans on the project website.
Hibernate Search version 5.4.0.CR1
is now available! It was built and tested with Hibernate ORM 5.0.0.CR2
,
essentially it’s all ready for ORM 5 and we’ll just be waiting for this to be marked Final
.
[ ... ]
Hibernate Search sends the indexing requests in the post transaction phase. Until now. The JMS backend can now send its indexing requests transactionally with the database changes. Why is that useful? Read on.
Sanne is going to do a virtual JBoss User Group session Tuesday July 14th at 6PM BST / 5PM UTC / 1PM EDT / 10 AM PDT. He is going to talk about Lucene in Java EE.
He will also describe some projects dear to our heart. If you want to know what Hibernate Search, Infinispan bring to the Lucene table and how they use Lucene internally, that’s the event to be in!
When creating a bug report for any project within the Hibernate family, it’s extremely helpful (and, frankly, required) to have an adequate test case available. This is obviously important to make reproducing the issue as easy as possible. But it’s also vital longer-term. Nearly every bug fix should include a regression test, which is frequently based on the original reproducer (sometimes, it’s the reproducer, verbatim).
To help create useful test cases, we’re opening up a repo with various templates. Please see the READMEs in each project’s subdir for more info: Hibernate Test Case Templates
As a starting point, the repo contains two templates for ORM:
For those of you using Hibernate ORM version 5.0.0.CR1, you can now use the freshly released Hibernate Search 5.4 version 5.4.0.Alpha1.