[hibernate-dev] [HSearch|OGM|Validator] Meeting and future meetings

[Emmanuel Bernard]

## Last meeting

Meeting ended Tue Feb 18 11:06:05 2014 UTC.  Information about MeetBot
at http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-02-18-09.21.html
Minutes (text):
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-02-18-09.21.txt
Log:
http://transcripts.jboss.org/meeting/irc.freenode.org/hibernate-dev/2014/hibernate-dev.2014-02-18-09.21.log.html

    /**
     * A query that generates the union of documents produced by its subqueries, and that scores each document with the maximum
     * score for that document as produced by any subquery, plus a tie breaking increment for any additional matching subqueries.
     * This is useful when searching for a word in multiple fields with different boost factors (so that the fields cannot be
     * combined equivalently into a single search field).  We want the primary score to be the one associated with the highest boost,
     * not the sum of the field scores (as BooleanQuery would give).
     * If the query is "albino elephant" this ensures that "albino" matching one field and "elephant" matching
     * another gets a higher score than "albino" matching both fields.
     * To get this result, use both BooleanQuery and DisjunctionMaxQuery:  for each term a DisjunctionMaxQuery searches for it in
     * each field, while the set of these DisjunctionMaxQuery's is combined into a BooleanQuery.
     * The tie breaker capability allows results that include the same term in multiple fields to be judged better than results that
     * include this term in only the best of those multiple fields, without confusing this with the better case of two different terms
     * in the multiple fields.
     */


## Futur meetings

We also decided to try a semimonthly meeting for the Non ORM side right
before the general Hibernate one.
Tuesday March 4th at is the next one.

Why not reuse the ORM one?
The timing is not very convenient for me and the discussions tend to
continue when I have to leave.
The main one tend to be quite full already.

Emmanuel