ry: <very long synonym expansion>
> > >
> > > the request took too long to iterate over terms. Timeout: timeoutAt:
> > > 812182664173653 (System.nanoTime(): 812182715745553),
> > > TermsEnum=org.apache.lucene.codecs.blocktree.SegmentTermsEnum@7a0db44
> >
> > o.a.s.s.SolrIndexSearcher Query: <very long synonym expansion>
> >
> > the request took too long to iterate over terms. Timeout: timeoutAt:
> > 812182664173653 (System.nanoTime(): 812182715745553),
> > TermsEnum=org.apache.lucene.codecs.blocktree.SegmentTermsE
gt;
> I have narrowed the problem down to the following:
> the way synonyms are being expaneded along with phrase slop.
>
> With a ps=5 I get 4096 possible permutations of the phrase being searched
> with because of synonyms, looking similar to:
> ngs_title:"bereavement lea
noTime(): 812182715745553),
TermsEnum=org.apache.lucene.codecs.blocktree.SegmentTermsEnum@7a0db441
I have narrowed the problem down to the following:
the way synonyms are being expaneded along with phrase slop.
With a ps=5 I get 4096 possible permutations of the phrase being searched
with because of synonyms, l
{!complexphrase inOrder=false}f: ( "cat jump"~2 ) this query will give
more result as it also consider "jump cat"~2 because inOrder=false,
inOrder=true may give you same result as f: ( "cat jump"~2)
or try f: ( "cat jump"~2 OR "jump cat"~2) to get same results as
{!complexphrase inOrder=false
Anyone have any insight here?
On 10/8/18, 3:34 PM, "David Santamauro" wrote:
Hi, quick question. Should
1) {!complexphrase inOrder=false}f: ( "cat jump"~2 )
... and
2) f: ( "cat jump"~2 )
... yield the same results? I'm trying to diagnose a more compl
Hi, quick question. Should
1) {!complexphrase inOrder=false}f: ( "cat jump"~2 )
... and
2) f: ( "cat jump"~2 )
... yield the same results? I'm trying to diagnose a more complicated
discrepancy that I've boiled down to this simple case. I understand #1 creates
a SpanQuery and #2 a PhraseQu
I've received a request from our business area to take a look at
emphasising ~0 phrase matches over ~1 (and greater) more that they are
already. I can't see any doco on the subject, and I'd like to ask if anyone
else has played in this area? Or at least is willing to sanity check my
reasoning befor
Hi Andre,
qs is used when you have explicit phrase query (you need to use quotes for
this) in your search string.
q="lisboa tipos"&qs=1
--- On Wed, 5/9/12, André Maldonado wrote:
> From: André Maldonado
> Subject: EDisMax and Query Phrase Slop Problem
> To: solr
hould default to doing some boost if none of the field lists is
> given, like boost using bigrams in the "qf" fields, but it doesn't.
>
> -- Jack Krupansky
>
> -Original Message- From: André Maldonado
> Sent: Wednesday, May 02, 2012 3:29 PM
> To: so
sage-
From: André Maldonado
Sent: Wednesday, May 02, 2012 3:29 PM
To: solr-user@lucene.apache.org
Subject: Phrase Slop probelm
Hi all.
In my index I have a multivalued field that contains a lot of information,
all text searches are based on it. So, When I Do:
http://xxx.xx.xxx.xxx:/Index/selec
; From: David Boxenhorn
> To: solr-user@lucene.apache.org
> Sent: Sun, October 10, 2010 5:02:01 AM
> Subject: Re: Query slop vs. phrase slop
>
> Thanks, Jonathan. Your explanation is very helpful.
>
> Can you explain exactly what you mean by "phrases created from the entire
ax's parameters.
>>>
>>> This is how I understand things, please tell me where I'm wrong:
>>>
>>> Query slop (qs) = how many words you can move the query to match the
>>> text.
>>> Phrase slop (ps) (when used in conjunction with &pf=t
ers.
This is how I understand things, please tell me where I'm wrong:
Query slop (qs) = how many words you can move the query to match the text.
Phrase slop (ps) (when used in conjunction with &pf=text - is there another
possibility?) = how many words you can move the text to match the query.
Ho
Got it!
Thanks a lot.
On Thu, Oct 7, 2010 at 3:00 PM, Ahmet Arslan wrote:
>
> > ps = ? - something that affects boosting, but how?
>
> Lets say your query is apache solr. (without quotation marks)
>
> Lets say these three documents contains all of these words and returned.
>
> 1-) solr is built
> ps = ? - something that affects boosting, but how?
Lets say your query is apache solr. (without quotation marks)
Lets say these three documents contains all of these words and returned.
1-) solr is built on the top of apache lucene.
2-) apache solr is fast, mature and popular.
3-) solr is hos
Thank you very much!
Forgive me, but I'm still having some trouble understanding:
qs = the maximum number of words apart the match can be
ps = ? - something that affects boosting, but how?
On Thu, Oct 7, 2010 at 12:57 PM, Ahmet Arslan wrote:
> phrase slop is about proximity search.
&g
phrase slop is about proximity search.
http://lucene.apache.org/java/2_4_0/queryparsersyntax.html#Proximity%20Searches
ps (Phrase Slop) affects boosting, if you play with ps value, numFound and
result set do not change. But the order of result set change. This is about the
phrase query that is
e query to match the text.
> Phrase slop (ps) (when used in conjunction with &pf=text - is there another
> possibility?) = how many words you can move the text to match the query.
>
> How are those two different in terms of the results they produce?
>
> On Tue, Oct 5, 2010 at
Thank you. I am talking about dismax's parameters.
This is how I understand things, please tell me where I'm wrong:
Query slop (qs) = how many words you can move the query to match the text.
Phrase slop (ps) (when used in conjunction with &pf=text - is there another
possibilit
> Can anyone explain to me the
> practical difference (i.e. in terms of results)
> between query slop and phrase slop?
I think you are asking about dismax's parameters, right?
ps (Phrase Slop) is about pf parameter.
qs (Query Phrase Slop) : You cannot use tilde operator with d
Can anyone explain to me the practical difference (i.e. in terms of results)
between query slop and phrase slop?
: Can I set the phrase slop value to standard request handler? I want it
: to be configurable in solrconfig.xml file.
if you mean when a user enters a query like...
+fieldA:"some phrase" +(fieldB:true fieldC:1234)
..you want to be able to control what slop value gets used
009 4:42:41 AM
> Subject: Phrase slop / Proximity search
>
> Can I set the phrase slop value to standard request handler? I want it
> to be configurable in solrconfig.xml file.
>
> Thanks,
> Siddharth
Can I set the phrase slop value to standard request handler? I want it
to be configurable in solrconfig.xml file.
Thanks,
Siddharth
: Subject: Re: Please Help !! Question about Query Phrase Slop (qs) in dismax
:
:
: Please help someone...i've been waiting for an answer for the last couple of
: days & no one seems to be helping out here. I did search the wiki & this
Please don't send messages like
: >From the solr wiki, it sounded like if qs is set to 5 for example, & if the
: search term is 'child custody', only docs with 'child' & 'custody' within 5
: words of one another would be returned in results. Is this correct? If so,
No. as explained on the wiki...
>> Amount of slop on phrase q
like if qs is set to 5 for example, & if
>>>> the search term is 'child custody', only docs with 'child' & 'custody'
>>>> within 5 words of one another would be returned in results. Is this
>>>> correct? If so, it doesn'
m is 'child custody', only docs with 'child' & 'custody'
>>> within 5 words of one another would be returned in results. Is this
>>> correct? If so, it doesn't seem to be working for me. I see docs with
>>> 'child' & &#
g stop
>> words) which is resulting in bad user experience as those docs are not so
>> relevant. What more could i do to improve quality in the results?
>>
>
> --
> View this message in context:
> http://www.nabble.com/Please-Help-%21%21-Question-about-Query-Phrase-Slop-%28qs%29-in-dismax-tp20643003p20654906.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
>
ore than 5 words of one another (excluding stop
> words) which is resulting in bad user experience as those docs are not so
> relevant. What more could i do to improve quality in the results?
>
--
View this message in context:
http://www.nabble.com/Please-Help-%21%21-Question-a
seem to be working for me. I see docs with
> 'child' & 'custody' more than 5 words of one another (excluding stop
> words) which is resulting in bad user experience as those docs are not so
> relevant. What more could i do to improve quality in the results?
>
m to be working for me. I see docs with 'child' & 'custody'
more than 5 words of one another (excluding stop words) which is resulting
in bad user experience as those docs are not so relevant. What more could i
do to improve quality in the results?
--
View this message in contex
On 9-Jan-08, at 2:16 PM, anuvenk wrote:
I have a ps of 10 set in the config. so for search terms like 'work
injury' ,
results that have work and injury within 10 words of one another
are coming
up in the first few results which is good. But it also returns
results that
have work and injury
h they are in page
8 or 9. But i'd like to know if there is a way wherein i could just tell
solr not to return results with the words from search term that are more
than 10 words apart.?
--
View this message in context:
http://www.nabble.com/phrase-slop-tp14723007p14723007.html
Sent from
: How does adding a phrase slop in the handler help?
: I tried ps=25 along with some pf values. I assumed that it means this..for
: eg: a search term, 'child custody battle' means documents which have the
: words 'child','custody','battle' within 25 words
ja
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
From: anuvenk <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Sunday, January 6, 2008 1:50:42 AM
Subject: Re: phrase slop param in dismax handler
The lower ps , the better or vice vers
; Otis
> --
> Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
>
> - Original Message
> From: anuvenk <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Saturday, January 5, 2008 4:05:00 AM
> Subject: phrase slop param in dismax handler
&g
ay, January 5, 2008 4:05:00 AM
Subject: phrase slop param in dismax handler
How does adding a phrase slop in the handler help?
I tried ps=25 along with some pf values. I assumed that it means
this..for
eg: a search term, 'child custody battle' means documents which have
the
words
How does adding a phrase slop in the handler help?
I tried ps=25 along with some pf values. I assumed that it means this..for
eg: a search term, 'child custody battle' means documents which have the
words 'child','custody','battle' within 25 words of one
40 matches
Mail list logo
