After chatting with Emmanuel, here is a draft plan for a closer integration between Hibernate and Lucene for performing full text queries.
Hibernate annotations for Lucene helps keeping the lucene indexes up to date, but doesn't provide a query facility.
It also lacks converters that would for
All sounds cool ;)
I can see the advantage of converters which can put elements into
Lucence in a better/human manner.
The loading of objects from Lucene + yet another QL I'm a bit more
critical about.
Would it not be better to do the following:
1. Use whatever QL Lucene supports to
About the QL :
You're right, the goal isn't to provide yet another QL, and Lucene's one should be used.
I meant having a Criteria type of QL, like what Compass does :CompassQueryBuilder queryBuilder = session.createQueryBuilder();
CompassHits hits = queryBuilder.bool()
.addMust(
On Jun 1, 2006, at 12:31 PM, Sylvain Vieujot wrote:
CompassHits hits = queryBuilder.bool() .addMust( queryBuilder.term
(name, jack) ) .addMustNot( queryBuilder.term(familyName,
london) ) .toQuery() .addSort(familyName,
CompassQuery.SortPropertyType.STRING) .addSort(birthdate,
On Thu, 01 Jun 2006 12:45:49 +0200, Christian Bauer
[EMAIL PROTECTED] wrote:
On Jun 1, 2006, at 12:31 PM, Sylvain Vieujot wrote:
CompassHits hits = queryBuilder.bool() .addMust( queryBuilder.term
(name, jack) ) .addMustNot( queryBuilder.term(familyName,
london) ) .toQuery()
I meant having a Criteria type of QL, like what Compass
does :CompassQueryBuilder queryBuilder = session.createQueryBuilder();
CompassHits hits = queryBuilder.bool()
.addMust( queryBuilder.term(name, jack) )
.addMustNot( queryBuilder.term(familyName, london) )
.toQuery()
