On 10/9/06, Tomi NA [EMAIL PROTECTED] wrote:
This is *exactly* what I was thinking. Like Stefan, I believe the
nutch analyzer is a good foundation and should therefore be extended
to support the or operator, and possibly additional capabilities
when the need arises.
t.n.a.
Tomi, why would
Hello,
I just would like to confirm that the version of the search() method
shown in the previous post works fine, at least regarding boolean
queries. Anyway, I see no reason why it wouldn't work with any other
Lucene query (fuzzy, proximity, etc.).
Now, please be warned that the inclusion of
Hi Björn,
yes, the error you point out will happen indeed... A possible
workaround would be:
public Hits search(String queryString, int numHits,
String dedupField, String sortField, boolean reverse)
throws IOException {
org.apache.lucene.queryParser.QueryParser parser =
