: 2) Submit to a different servlet of my own design, which interprets the
: form input, forms the Lucene query string, adds it to a SOLR request
: URL, gets the output of the REST response and does something with it,
: probably doing an XSLT transformation. This method resembles how my old
: app
: > title:(gone with the wind)^3.0 OR title2:(gone with the wind)
: That did it! Thanks for the Help!
: What value do the numbers carry in the ranking? I arbitrarily choose
: the number 5 cause it's an easy number :)
query boosts are in fact pretty arbitrary ... what you should pick really
depe
On 1/25/07, Walter Lewis <[EMAIL PROTECTED]> wrote:
I ran the debug against the two following queries:
q=(James Sutherland) returns 13
q=(James~0.75 Sutherland~0.75) returns 1
OK, I have an idea of what's going on... here are your two parsed
queries side by side:
+(+text:jame +text:sut
Yonik Seeley wrote:
On 1/23/07, Walter Lewis <[EMAIL PROTECTED]> wrote:
This is quite possibly a Lucene question rather than a solr one, so my
apologies if you think its out of scope.
Underlying the solr search, are some very useful Lucene constructs.
One of the most powerful, imho, is the til
Yonik Seeley wrote:
What about term ranking, could I rank the phrases searched in title
higher than title2?
Absolutely... standard lucene syntax for boosting will give you that
in the standard query handler.
title:(gone with the wind)^3.0 OR title2:(gone with the wind)
That did it! Thanks f
