Merry Christmas and a happy New Year, everyone!
It is a great pleasure to work with such an amazing bunch of people,
looking forward to tackle many more exciting things with you in 2016!
Am 24.12.2015 11:50 schrieb "Emmanuel Bernard" <emmanuel(a)hibernate.org>:
Merry Christmas, enjoy your holidays :)
> On 24 Dec 2015, at 10:12, Vlad Mihalcea <mihalcea.vlad(a)gmail.com> wrote:
> Merry Christmas guys and have a great time during the winter holidays.
> hibernate-dev mailing list
hibernate-dev mailing list
3 days from Christmas we decided to release Hibernate OGM as a present.
The major news in this release are:
- mapping support for Cassandra 2.2 new data types
- proper handling of the @Lob annotation
- post-load event support using @PostLoad annotation
- Infinispan 8
- Hibernate Search 5.5
You can find all the details about this release and what's coming next in
the blog post .
Many thanks to all the people that helped us make this release possible.
Assuming you build a Lucene Query the following way:
queryBuilder.keyword().onField( "age" ).matching( 5 ).createQuery();
What is your expectation, if the "age" field is being indexed as a NumericField?
we generally have been trying to target the versions of Infinispan
provided by the WildFly version we're targeting for compatibility with
a specific OGM release cycle.
I would like to change that, and for example now switch to the latest
Infinispan 8.1.0.Final (rather than the one in WildFly 10 candidate
release, which would be 8.0.2.Final).
# shall not use the WildFly Infinispan distribution
in WildFly the specific Infinispan version being integrated is an
People wanting to use Infinispan directly, or for other means than the
ones addressed by the WildFly clustering features which are based on
Infinispan (but don't expose it), should be encouraged to download the
Infinispan modules from the Infinispan project. We should apply (and
encourage) this practice too.
# pick our own version
it's obviously nicer for us to reserve ourselves the practical
benefits of being able to pick our own version according to needs,
rather than stick with wathever WildFly requires.
# we might have a need for latest Infinispan
probably no need to explain ;)
I don't with us to wait for an app-server update cycle when we need an
# don't aim at a single WildFly version
while we're currently running integration tests with latest WildFly,
I think it's desirable to use that as a testing bed for the modules we
provide but not as a coupling factor for our dependency matrix.
In other words, let's prepare OGM to be able to produce modules for
different versions of the application servers (and not least other
application servers although that's unrelated).
Not least, the fact that the app server is sticking with some version
shouldn't have an impact to all of our users who have no interest in
this particular appserver at all.
Am I missing any important counter argument?
Is anyone banning users from the forum? I am getting "A ban has been
issued on your IP address."
I don't think banning by IP is a good strategy as many users will have
dynamic IPs from their hoster's shared pool, so it's a random game to
hit an IP previously banned due to some other user's spam.
Apache Lucene 5.4.0 is released as stable, and while it includes
several benefits - not least a performance fix from myself which I'd
be keen to take advantage of - there are no significant changes
visible to end users, expect I think this one is worth a warning:
LUCENE-6590: Query.setBoost(), Query.getBoost() and Query.clone() are
gone. In order to apply boosts, you now need to wrap queries in a
Although, it doesn't affect any of our code not examples so a release
note might be acceptable.
There are several other interesting performance improvements.
So I'm tempted to upgrade to this version in the next maintenance
(micro) release of Hibernate Search 5.5.
What do you all think about that?
I have been working on a change to the pooled optimizer that we have been seeing good performance results with. Basically it hands out blocks of ID's to a thread local, rather than having every thread contend on the lock every time an ID is required.
What would I need to do to get a change like this in? In particular:
- Does it need to be a new type of optimizer, or is modifying the existing one like I have done OK?
- How should it be configured?
I am happy to do up a PR for this, but I am just not really sure what would be required to get it to a point where it would be acceptable for inclusion.