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.
While our focus has been on the exciting new improvements in Hibernate Search 4, since the release of the last stable release 3.4.0.Final we had much interesting feedback from the community, including bugreports and patches.
The release cycle of Hibernate Search 4 has begun. Alpha 1 is out. We already have many things implemented so this change is consistent and more releases will come quickly.
As every month, we're having a JBoss user group meeting in Newcastle. Next Tuesday 12th July at 6pm I'll be presenting
We decided to insert another candidate release in the roadmap for two improvements which where too good to leave out
One week after 3.4.0.Beta1, two weeks after 3.4.0.Alpha1, we're on a run for 3.4.0.Final!
We did a big refactoring of the query engine, hence the alpha tag. If you could focus your tests in this area and see if there are any issues, we would be forever grateful.
One of the points for using Hibernate Search is that your valued business data is stored in the database: a reliable transactional and relational store. So while Hibernate Search keeps the index in sync with the database during regular use, in several occasions you'll need to be able to rebuild the indexes from scratch: