[search] QueryBuilder "or" request

elendrim · **Posted:** Thu Dec 30, 2010 12:18 pm

Hello,

I want to make a request like this using the QueryBuilder ( new in hibernate search ).
" state:hidden OR state:frozen OR state:published AND hidden:false "

I try something, but it's not working :

Code:

SessionFactory sessionFactory = HibernateUtil.getSessionFactory();
FullTextSession ftSession = Search.getFullTextSession(sessionFactory.getCurrentSession());
QueryBuilder mythQB = ftSession.getSearchFactory().buildQueryBuilder().forEntity( Product.class ).get();
String[] states = {"frozen","published"};
BooleanJunction<BooleanJunction> b = mythQB.bool();
for (String state : states) {
    b.should(
        mythQB.keyword().onField("state").matching(state).createQuery()
    );
}

b.must(
    mythQB.keyword().onField("hidden").matching(String.valueOf(hidden)).createQuery()
);

Also, is it possible to view the query passed to lucene using the query builder ?

hardy.ferentschik · **Posted:** Thu Dec 30, 2010 12:56 pm

this query

Quote:

state:hidden OR state:frozen OR state:published AND hidden:false

is really equivalent to the query:

Code:

state:hidden OR state:frozen OR (state:published AND hidden:false)

Your programmatic query is equivalent to:

Code:

(state:hidden OR state:frozen) AND hidden:false

Could that be the problem?

elendrim · **Posted:** Thu Dec 30, 2010 1:17 pm

No my problem is not in the lucene query, but in the QueryBuilder.
If you prefer I need this request :

Code:

( state:hidden OR state:frozen OR state:published ) AND hidden:false

But using the Querybuilder, and b.should is not equivalent to OR.

sanne.grinovero · **Posted:** Sat Jan 01, 2011 9:26 am

Quote:

But using the Querybuilder, and b.should is not equivalent to OR.

Why? Should "should behave like" OR
The QueryBuilder is using the "should" term which is more appropriate, also if you build the Query programmatically
via Lucene's org.apache.lucene.search.BooleanClause the OR operator is named "should" which is more appropriate than "OR".
Only the queryParses uses the "OR" name, mostly legacy and ease of use of non-technical query writers (like to parse user input queries).

What makes you think that they are not being equivalent?

elendrim · **Posted:** Mon Jan 03, 2011 7:02 am

Ok, I didn't understand that.
You've right.

I'm using this for my request :

Code:

SessionFactory sessionFactory = HibernateUtil.getSessionFactory();
FullTextSession ftSession = Search.getFullTextSession(sessionFactory.getCurrentSession());
QueryBuilder mythQB = ftSession.getSearchFactory().buildQueryBuilder().forEntity( Product.class ).get();
String[] states = {"frozen","published"};
BooleanJunction<BooleanJunction> b = mythQB.bool();
BooleanQuery bQuery = new BooleanQuery();
for (String state : states) {
    bQuery.add( mythQB.keyword().onField("state").matching(state).createQuery(), Occur.SHOULD) ;
}

b.must(bQuery);

b.must(
    mythQB.keyword().onField("hidden").matching(String.valueOf(hidden)).createQuery()
);

FullTextQuery ftquery = ftSession .createFullTextQuery( b.createQuery(), Product.class );
List<LogicalItem> results = ftquery.setFirstResult( firstResult ) .setMaxResults( maxResults ).list();
int resultSize = ftquery.getResultSize();

sanne.grinovero · **Posted:** Mon Jan 03, 2011 7:18 am

Hi elendrim,
is your problem solved? Works as expected?

Remembed when using the BooleanQuery like that you have to provide pre-Analyzed/Tokenized strings, so your solutions should work fine but is a bit verbose and tricky as you have to match the indexing analyzer. that's what the DSL is doing for you.

elendrim · **Posted:** Tue Jan 04, 2011 10:42 am

Yes, my problem is solved,
Thank you ;)