I'm working in the Hibernate and Infinispan teams at Red Hat, caring about Lucene integration in products we support, striving to make it easier to use and to integrate in well known APIs and patterns, and finally to make it scale better; I love clean and well performing code. I've been an early adopter of cloud deployments scaling Lucene to a large number of requests on Amazon EC2 using Hibernate Search, and after that I worked with JIRA to make it clusterable via Infinispan. I've lived in Holland, Italy, the Dominican Republic, Chile, Portugal and the UK; love OSS and socializing with other developers to improve all and any OSS project.
Having fixed several issues and tasks since the previous milestone, it’s time to publish our third milestone towards Elasticsearch integration: Hibernate Search version 5.6.0.Alpha3 is now available!
Today we’re proud to announce the first Alpha release sporting experimental integration with Elasticsearch!
We also updated to use Apache Lucene 5.5 - the latest stable release of our favourite search engine - as of course we’re not abandoning our traditional users!
5.5.2.Final is now available, our latest stable version sporting integration with Hibernate ORM 5 and Apache Lucene 5.3 - the state of the art.
Creating this version to be compatible with these two great OSS projects kept us busy for a good deal of this past year; I remember discussing this option with superstar OSS contributors Uwe Schindler (Apache Lucene developer) and Gustavo Nalle (Infinispan developer) at FOSDEM in January 2015! I am grateful to both for their guidance and suggestions, as driving progress forward is sometimes challenging when we strive to keep backwards compatibility as best as we can.
On top of that, our same small but amazing team as been working hard on Hibernate OGM 5, a bit of Hibernate Validator, incredible performance improvements on Hibernate ORM "classic" and is still tinkering on the internals of Hibernate Search to make an Elasticsearch backend an alternative to plain Lucene.
Hibernate Search 5.5.1.Final is now available!
Feedback about our recent
5.5.0.Final release has been great, and while the good news is that nobody reported significant issues,
some people also pointed out that the new sorting system was a bit limited.
So we’ve been working on enhancing the
FieldBridge API to make sure that those more expert users who implement their
own bridging would have a better control on how sorting works as well.
We’ve also started some work to push the performance higher, and overall I’m proud to state that this
is including some small internal polish, but results in measurable improvements.
The first Candidate Release for Hibernate Search 5.5 is now available, introducing integration with
Apache Lucene 5.3
and several nice improvements.
As a reminder on versions: Hibernate Search now requires
Hibernate ORM 5.0.0.Final at least, and at the time of writing only
Infinispan 8.0.1.Final supports real time replication of an
Apache Lucene 5.3 index.
[ ... ]
After two candidate releases and a bit of quiet time in waiting for Hibernate ORM 5.0.0.Final,
we now published
Hibernate Search 5.4.0.Final: the first stable release compatible with ORM 5.
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.
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.
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
[ ... ]