The default query parser that comes with luwak just uses the standard lucene query parser, which will understand boolean syntax and boosting. Just be aware that the standard lucene scoring model doesn’t make a great deal of sense in this case, because each query is run across an index consisting of a single document, so the IDF value will always be 1. You can set the Similarity model to be used when constructing an InputDocument if you want to use a different model, and then retrieve scores using a ScoringMatcher.

The lucene query parser doesn’t support geosearches at the moment (although there is some work being done to include simple geospatial syntax, see https://issues.apache.org/jira/browse/LUCENE-6450), so if you want to add these type of queries you’ll have to write a new query parser. It should be possible to extend the standard parser to this end.

I’ve built the luwak master-5.1 branch from https://github.com/flaxsearch/luwak/tree/master-5.1 and it works perfect for me.

Here are my queries and documents.
query_01 = [Toyota Camry 2002]
query_02 = [Tesla model S]
…

document_01 = [Need a BMW i528 2000 in San Francisco, CA 94105]
document_02 = [Looking for a tesla in Mountain View, CA 94043]
…

The luwak engine found:
document_02 is matched query_02

I’m impressed with the luwak performance. For instance: 1,000,000 queries against 20 documents took only ~104seconds.

So I want to say a big thank you to all of you who have worked on this project and would like to ask the following questions:

1) Can I provide a query like this to the luwak engine?
query_n = [(+honda +volvo )^2.75 (+camry +bmw )^0.75 ]

As you see, I have the power term “^2.75” in my query, that means a particular key word is 2.75 times important than other key words in the query. So my question is does the luwak engine recognize those kind of syntaxes?

2) Also I would like to add a geo param such as latitude, longtitude and raduis to queries. Is it possible? If yes, please provide tools/plugins/links/materials.

Best,
Bakhy

At the moment luwak is a standalone library, rather than integrated directly into Solr. It will work with any lucene Query object, and you can plug in one of the Solr query parsers if you like. Filter queries don’t make so much sense with luwak, as the queries are only ever run over a single document.

Do let us know more about your use case directly if you like via http://www.flax.co.uk/contact/

Charlie