http://pastebin.com/svyefmM6
Pretty standard :)
/Tor
On Mon, May 16, 2011 at 9:18 AM, lboutros wrote:
> The analyzer of the field you are using could impact the Phrase Query Slop.
> Could you copy/paste the part of the schema ?
>
> Ludovic.
>
> -
> Jouve
> France.
> --
> View this message i
The analyzer of the field you are using could impact the Phrase Query Slop.
Could you copy/paste the part of the schema ?
Ludovic.
-
Jouve
France.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Order-of-words-in-proximity-search-tp2938427p2946764.html
Sent from the Solr
Hi,
The strange part is that i have actually tried a slop of 1000 (1K),
and the results are still different. This even when the test data has
a limiter of 10K for each sentence.
(This means that a sloppy phrase should only give hits where the
complete sentence is found, yet it is not the result...
I would prefer to put a higher slop number instead of a boolean clause : 200
perhaps in your specific case.
Ludovic.
-
Jouve
France.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Order-of-words-in-proximity-search-tp2938427p2946645.html
Sent from the Solr - User mailing
the key phrase was this one :) :
"A sloppy phrase query specifies a maximum "slop", or the number of
positions tokens need to be moved to get a match. "
so you could search for "foo bar"~101 in your example.
Ludovic.
-
Jouve
France.
--
View this message in context:
http://lucene.472066.n3
Hi,
That only explains how to do it, not even that document specifies that
order actually has something to say. :)
"batman movie"~100 will give other results than "movie batman"~100.
/Tor
On Sun, May 15, 2011 at 7:18 PM, lboutros wrote:
> Hi,
>
> see here for an explanation :
>
> http://wiki.ap
Hi,
see here for an explanation :
http://wiki.apache.org/solr/SolrRelevancyFAQ#How_can_I_search_for_one_term_near_another_term_.28say.2C_.22batman.22_and_.22movie.22.29
Ludovic.
-
Jouve
France.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Order-of-words-in-proximity-
Hello,
Thanks for the replay.
Just as i suspected. So the solution then is to create a OR search
with both possibilities in order to make the order not be important"
"foo bar"~100 -> ("foo bar~100 OR "bar foo"~100)
--
Best regards
Tor Henning Ueland
On Sun, May 15, 2011 at 5:16 PM, Erick Eri
Yes, order does matter. When order is changed as in your example, matching the
text "foo always bar" would require one more move for "bar foo" than
for "foo bar"
Lucene In Action has some nice graphics explaining this
Best,
Erick
On Fri, May 13, 2011 at 6:13 AM, Tor Henning Ueland
wrote:
> H
