Version 5.0.0.CR1 of Hibernate Search is now available.
Numeric Field(s) being used by default
If you don't specify any FieldBridge for your Numeric attributes, or Date or Calendar fields, now Hibernate Search will encode them by default using Lucene's specialized NumericField format. This format was available since long in both Lucene and Hibernate Search, but so far you had to explicitly enable it as Hibernate Search would - by default - stick to the backwards compatible format of transforming these types into keywords (strings). The NumericField format is much more efficient to perform range queries - which we expect being common for these types.
Remember that - unless you had explicit field configuration - this implies that you might need to fix how your queries are created. By using the Hibernate Search Query DSL you will get an exception to warn you if you try to force it using the wrong type. If you're using the Lucene API directly, make sure to check you're getting the results you expect.
API changes
I have no other major changes to report regarding our public API; however for power users and other frameworks integrating with Hibernate Search you might notice a significant reorganization of our SPI. We've documented all relevant changes in the Migration Guide.
The final release of version 5 will be released very soon, so please make sure you test this quickly. Any comment is welcome on the mailing list or via IRC.
Sanne
