You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Vadim Kisselmann <v....@googlemail.com> on 2012/01/31 13:53:11 UTC
Edismax, Filter Query and Highlighting
Hi,
i have problems with edismax, filter queries and highlighting.
First of all: can edismax deal with filter queries?
My case:
Edismax is my default requestHandler.
My query in SolrAdminGUI: (roomba OR irobot) AND language:de
You can see, that my q is "roomba OR irobot" and my fq is
"language:de"(language is a field in schema.xml)
With this params i turn highlighting on: &hl=true&hl.fl=text,title,url
In my shown result you can see that highlighting matched on
<em>de</em> in url(last <arr>).
<lst name="de.blog-gedanken/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger">
<arr name="title"><str>Erste Erfahrung mit unserem <em>Roomba</em>
Roboter Staubsauger</str></arr>
<arr name="text"><str>
Erste Erfahrung mit unserem <em>Roomba</em> Roboter Staubsauger
Tags: Haushaltshilfe, Roboter</str></arr>
<arr name="url"><str>http://www.blog-gedanken.<em>de</em>/produkte/erste-erfahrung-mit-unserem-<em>roomba</em>-roboter-staubsauger/</str></arr></lst>
in calalina.out i can see the following query:
path=/select/ params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
hits=1 status=0 QTime=65
language:de is a filter, and shouldn't be highlighted.
Do i have a thinking error, or is my query wrong? Or is it an edismax problem?
Vest Regards
Vadim
Re: Edismax, Filter Query and Highlighting
Posted by Vadim Kisselmann <v....@googlemail.com>.
hl.q works:)
But i have to attach the hl.q to my standard query.
In bigger queries it would by a pain to find out, which terms i need in my hl.q.
My plan: Own query parser in solr, which loops through q, identifies
filter terms(in my case language:de) and append
it as hl.q to the standard query. Sounds like a plan? :)
Best Regards
Vadim
2012/2/1 Koji Sekiguchi <ko...@r.email.ne.jp>:
> (12/02/01 4:28), Vadim Kisselmann wrote:
>>
>> Hmm, i don´t know, but i can test it tomorrow at work.
>> i´m not sure about the right syntax with hl.q. (?)
>> but i report :)
>
>
> hl.q can accept same syntax of q, including local params.
>
> koji
> --
> http://www.rondhuit.com/en/
Re: Edismax, Filter Query and Highlighting
Posted by Koji Sekiguchi <ko...@r.email.ne.jp>.
(12/02/01 4:28), Vadim Kisselmann wrote:
> Hmm, i don´t know, but i can test it tomorrow at work.
> i´m not sure about the right syntax with hl.q. (?)
> but i report :)
hl.q can accept same syntax of q, including local params.
koji
--
http://www.rondhuit.com/en/
Re: Edismax, Filter Query and Highlighting
Posted by Vadim Kisselmann <v....@googlemail.com>.
Hmm, i don´t know, but i can test it tomorrow at work.
i´m not sure about the right syntax with hl.q. (?)
but i report :)
2012/1/31 Ahmet Arslan <io...@yahoo.com>:
>> > Try the &fq option maybe?
>>
>> I thought so, unfortunately.
>> &fq will be the only option. I should rebuild my
>> application :)
>
> Could hl.q help? http://wiki.apache.org/solr/HighlightingParameters#hl.q
Re: Edismax, Filter Query and Highlighting
Posted by Ahmet Arslan <io...@yahoo.com>.
> > Try the &fq option maybe?
>
> I thought so, unfortunately.
> &fq will be the only option. I should rebuild my
> application :)
Could hl.q help? http://wiki.apache.org/solr/HighlightingParameters#hl.q
Re: Edismax, Filter Query and Highlighting
Posted by Vadim Kisselmann <v....@googlemail.com>.
Hi Erick,
> I didn't read your first post carefully enough, I was keying
> on the words "filter query". Your query does not have
> any filter queries! I thought you were talking
> about &fq=language:de type clauses, which is what
> I was responding to.
no problem, i understand:)
> Solr/Lucene have no way of
> interpreting an extended "q" clause and saying
> "this part is a query and should be highlighted and
> this part isn't".
>
> Try the &fq option maybe?
I thought so, unfortunately.
&fq will be the only option. I should rebuild my application :)
Best Regards
Vadim
Re: Edismax, Filter Query and Highlighting
Posted by Erick Erickson <er...@gmail.com>.
I didn't read your first post carefully enough, I was keying
on the words "filter query". Your query does not have
any filter queries! I thought you were talking
about &fq=language:de type clauses, which is what
I was responding to. Solr/Lucene have no way of
interpreting an extended "q" clause and saying
"this part is a query and should be highlighted and
this part isn't".
Try the &fq option maybe?
Best
Erick
On Tue, Jan 31, 2012 at 10:08 AM, Vadim Kisselmann
<v....@googlemail.com> wrote:
> Hi Erick,
> thanks for your response:)
>
> Here its my query:
> (roomba OR irobot) AND language:de AND
> url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"
> Url and language are fields in my schema.xml
>
> With &hl=true&hl.fl=text,url i see this, but i want only see "roomba"
> or "robot" highlighted:
> <arr name="url"><str><em>http</em>://<em>www</em>.<em>blog</em>-<em>gedanken</em>.<em>de</em>/<em>produkte</em>/<em>erste</em>-<em>erfahrung</em>-<em>mit</em>-<em>unserem</em>-<em>roomba</em>-<em>roboter</em>-<em>staubsauger</em>/</str></arr>
>
> you see, the whole url is highlighted.
>
> with debugQuery=on:
>
> <lst name="debug"><str name="rawquerystring">(roomba OR irobot) AND
> language:de AND
> url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"</str>
> <str name="querystring">(roomba OR irobot) AND language:de AND
> url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"</str>
> <str name="parsedquery">(+(+(DisjunctionMaxQuery((title:roomba)~0.01)
> DisjunctionMaxQuery((title:irobot)~0.01)) +language:de
> +PhraseQuery(url:"http www blog gedanken de produkte erste erfahrung
> mit unserem roomba roboter staubsauger"))
> DisjunctionMaxQuery((text:"roomba irobot"~100)~0.01))/no_coord</str>
> <str name="parsedquery_toString">+(+((title:roomba)~0.01
> (title:irobot)~0.01) +language:de +url:"http www blog gedanken de
> produkte erste erfahrung mit unserem roomba roboter staubsauger")
> (text:"roomba irobot"~100)~0.01</str>
> <lst name="explain"><str
> name="de.blog-gedanken/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger">
> 26.130154 = (MATCH) sum of:
> 26.130154 = (MATCH) sum of:
> 0.30008852 = (MATCH) product of:
> 0.60017705 = (MATCH) sum of:
> 0.60017705 = (MATCH) weight(title:roomba in 199491)
> [DefaultSimilarity], result of:
> 0.60017705 = score(doc=199491,freq=1.0 = termFreq=1
> ), product of:
> 0.119503364 = queryWeight, product of:
> 13.392695 = idf(docFreq=19, maxDocs=4820692)
> 0.008923026 = queryNorm
> 5.0222607 = fieldWeight in 199491, product of:
> 1.0 = tf(freq=1.0), with freq of:
> 1.0 = termFreq=1
> 13.392695 = idf(docFreq=19, maxDocs=4820692)
> 0.375 = fieldNorm(doc=199491)
> 0.5 = coord(1/2)
> 0.08084078 = (MATCH) weight(language:de in 199491)
> [DefaultSimilarity], result of:
> 0.08084078 = score(doc=199491,freq=1.0 = termFreq=1
> ), product of:
> 0.026857855 = queryWeight, product of:
> 3.0099492 = idf(docFreq=645950, maxDocs=4820692)
> 0.008923026 = queryNorm
> 3.0099492 = fieldWeight in 199491, product of:
> 1.0 = tf(freq=1.0), with freq of:
> 1.0 = termFreq=1
> 3.0099492 = idf(docFreq=645950, maxDocs=4820692)
> 1.0 = fieldNorm(doc=199491)
> 25.749224 = (MATCH) weight(url:"http www blog gedanken de produkte
> erste erfahrung mit unserem roomba roboter staubsauger" in 199491)
> [DefaultSimilarity], result of:
> 25.749224 = score(doc=199491,freq=1.0 = phraseFreq=1.0
> ), product of:
> 0.9586678 = queryWeight, product of:
> 107.43752 = idf(), sum of:
> 1.0006605 = idf(docFreq=4817508, maxDocs=4820692)
> 1.4342768 = idf(docFreq=3122520, maxDocs=4820692)
> 4.5387235 = idf(docFreq=140042, maxDocs=4820692)
> 10.954706 = idf(docFreq=228, maxDocs=4820692)
> 3.1167865 = idf(docFreq=580497, maxDocs=4820692)
> 9.476681 = idf(docFreq=1003, maxDocs=4820692)
> 9.195494 = idf(docFreq=1329, maxDocs=4820692)
> 11.576243 = idf(docFreq=122, maxDocs=4820692)
> 6.3489246 = idf(docFreq=22913, maxDocs=4820692)
> 12.31089 = idf(docFreq=58, maxDocs=4820692)
> 13.392695 = idf(docFreq=19, maxDocs=4820692)
> 11.229373 = idf(docFreq=173, maxDocs=4820692)
> 12.862067 = idf(docFreq=33, maxDocs=4820692)
> 0.008923026 = queryNorm
> 26.85938 = fieldWeight in 199491, product of:
> 1.0 = tf(freq=1.0), with freq of:
> 1.0 = phraseFreq=1.0
> 107.43752 = idf(), sum of:
> 1.0006605 = idf(docFreq=4817508, maxDocs=4820692)
> 1.4342768 = idf(docFreq=3122520, maxDocs=4820692)
> 4.5387235 = idf(docFreq=140042, maxDocs=4820692)
> 10.954706 = idf(docFreq=228, maxDocs=4820692)
> 3.1167865 = idf(docFreq=580497, maxDocs=4820692)
> 9.476681 = idf(docFreq=1003, maxDocs=4820692)
> 9.195494 = idf(docFreq=1329, maxDocs=4820692)
> 11.576243 = idf(docFreq=122, maxDocs=4820692)
> 6.3489246 = idf(docFreq=22913, maxDocs=4820692)
> 12.31089 = idf(docFreq=58, maxDocs=4820692)
> 13.392695 = idf(docFreq=19, maxDocs=4820692)
> 11.229373 = idf(docFreq=173, maxDocs=4820692)
> 12.862067 = idf(docFreq=33, maxDocs=4820692)
> 0.25 = fieldNorm(doc=199491)
> </str></lst><str name="QParser">ExtendedDismaxQParser</str><null
> name="altquerystring"/><null name="boostfuncs"/><lst
> name="timing"><double name="time">16.0</double><lst
> name="prepare"><double name="time">0.0</double><lst
> name="org.apache.solr.handler.component.QueryComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.FacetComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.MoreLikeThisComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.HighlightComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.StatsComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.DebugComponent"><double
> name="time">0.0</double></lst></lst><lst name="process"><double
> name="time">15.0</double><lst
> name="org.apache.solr.handler.component.QueryComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.FacetComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.MoreLikeThisComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.HighlightComponent"><double
> name="time">8.0</double></lst><lst
> name="org.apache.solr.handler.component.StatsComponent"><double
> name="time">0.0</double></lst><lst
> name="org.apache.solr.handler.component.DebugComponent"><double
> name="time">7.0</double></lst></lst></lst></lst>
>
> I hope you can read it:)
>
> Best Regards
> Vadim
>
>
>
>
>
> 2012/1/31 Erick Erickson <er...@gmail.com>:
>> Seeing the results with &debugQuery=on would help.
>>
>> No, fq does NOT get translated into q params, it's a
>> completely separate mechanism so I'm not quite sure
>> what you're seeing.
>>
>> Best
>> Erick
>>
>> On Tue, Jan 31, 2012 at 8:40 AM, Vadim Kisselmann
>> <v....@googlemail.com> wrote:
>>> Hi Ahmet,
>>>
>>> thanks for quick response :)
>>> I've also discovered this failure.
>>> I wonder that the query themselves works.
>>> For example: query = language:de
>>> I get results which only have language:de.
>>> Also works the fq and i get only the "de"-result in my field "language".
>>> I can't understand the behavior. It seems like the fq works, but at
>>> the end my fq-params be converted to q-params.
>>>
>>> Regards
>>> Vadim
>>>
>>>
>>>
>>> 2012/1/31 Ahmet Arslan <io...@yahoo.com>:
>>>>> in calalina.out i can see the following query:
>>>>> path=/select/
>>>>> params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
>>>>> hits=1 status=0 QTime=65
>>>>>
>>>>> language:de is a filter, and shouldn't be highlighted.
>>>>> Do i have a thinking error, or is my query wrong? Or is it
>>>>> an edismax problem?
>>>>
>>>> In your example, language:de is a part of query. Use &fq= instead.
>>>> q=(roomba OR irobot)&fq=language:de
>>>>
Re: Edismax, Filter Query and Highlighting
Posted by Vadim Kisselmann <v....@googlemail.com>.
Hi Erick,
thanks for your response:)
Here its my query:
(roomba OR irobot) AND language:de AND
url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"
Url and language are fields in my schema.xml
With &hl=true&hl.fl=text,url i see this, but i want only see "roomba"
or "robot" highlighted:
<arr name="url"><str><em>http</em>://<em>www</em>.<em>blog</em>-<em>gedanken</em>.<em>de</em>/<em>produkte</em>/<em>erste</em>-<em>erfahrung</em>-<em>mit</em>-<em>unserem</em>-<em>roomba</em>-<em>roboter</em>-<em>staubsauger</em>/</str></arr>
you see, the whole url is highlighted.
with debugQuery=on:
<lst name="debug"><str name="rawquerystring">(roomba OR irobot) AND
language:de AND
url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"</str>
<str name="querystring">(roomba OR irobot) AND language:de AND
url:"http://www.blog-gedanken.de/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger/"</str>
<str name="parsedquery">(+(+(DisjunctionMaxQuery((title:roomba)~0.01)
DisjunctionMaxQuery((title:irobot)~0.01)) +language:de
+PhraseQuery(url:"http www blog gedanken de produkte erste erfahrung
mit unserem roomba roboter staubsauger"))
DisjunctionMaxQuery((text:"roomba irobot"~100)~0.01))/no_coord</str>
<str name="parsedquery_toString">+(+((title:roomba)~0.01
(title:irobot)~0.01) +language:de +url:"http www blog gedanken de
produkte erste erfahrung mit unserem roomba roboter staubsauger")
(text:"roomba irobot"~100)~0.01</str>
<lst name="explain"><str
name="de.blog-gedanken/produkte/erste-erfahrung-mit-unserem-roomba-roboter-staubsauger">
26.130154 = (MATCH) sum of:
26.130154 = (MATCH) sum of:
0.30008852 = (MATCH) product of:
0.60017705 = (MATCH) sum of:
0.60017705 = (MATCH) weight(title:roomba in 199491)
[DefaultSimilarity], result of:
0.60017705 = score(doc=199491,freq=1.0 = termFreq=1
), product of:
0.119503364 = queryWeight, product of:
13.392695 = idf(docFreq=19, maxDocs=4820692)
0.008923026 = queryNorm
5.0222607 = fieldWeight in 199491, product of:
1.0 = tf(freq=1.0), with freq of:
1.0 = termFreq=1
13.392695 = idf(docFreq=19, maxDocs=4820692)
0.375 = fieldNorm(doc=199491)
0.5 = coord(1/2)
0.08084078 = (MATCH) weight(language:de in 199491)
[DefaultSimilarity], result of:
0.08084078 = score(doc=199491,freq=1.0 = termFreq=1
), product of:
0.026857855 = queryWeight, product of:
3.0099492 = idf(docFreq=645950, maxDocs=4820692)
0.008923026 = queryNorm
3.0099492 = fieldWeight in 199491, product of:
1.0 = tf(freq=1.0), with freq of:
1.0 = termFreq=1
3.0099492 = idf(docFreq=645950, maxDocs=4820692)
1.0 = fieldNorm(doc=199491)
25.749224 = (MATCH) weight(url:"http www blog gedanken de produkte
erste erfahrung mit unserem roomba roboter staubsauger" in 199491)
[DefaultSimilarity], result of:
25.749224 = score(doc=199491,freq=1.0 = phraseFreq=1.0
), product of:
0.9586678 = queryWeight, product of:
107.43752 = idf(), sum of:
1.0006605 = idf(docFreq=4817508, maxDocs=4820692)
1.4342768 = idf(docFreq=3122520, maxDocs=4820692)
4.5387235 = idf(docFreq=140042, maxDocs=4820692)
10.954706 = idf(docFreq=228, maxDocs=4820692)
3.1167865 = idf(docFreq=580497, maxDocs=4820692)
9.476681 = idf(docFreq=1003, maxDocs=4820692)
9.195494 = idf(docFreq=1329, maxDocs=4820692)
11.576243 = idf(docFreq=122, maxDocs=4820692)
6.3489246 = idf(docFreq=22913, maxDocs=4820692)
12.31089 = idf(docFreq=58, maxDocs=4820692)
13.392695 = idf(docFreq=19, maxDocs=4820692)
11.229373 = idf(docFreq=173, maxDocs=4820692)
12.862067 = idf(docFreq=33, maxDocs=4820692)
0.008923026 = queryNorm
26.85938 = fieldWeight in 199491, product of:
1.0 = tf(freq=1.0), with freq of:
1.0 = phraseFreq=1.0
107.43752 = idf(), sum of:
1.0006605 = idf(docFreq=4817508, maxDocs=4820692)
1.4342768 = idf(docFreq=3122520, maxDocs=4820692)
4.5387235 = idf(docFreq=140042, maxDocs=4820692)
10.954706 = idf(docFreq=228, maxDocs=4820692)
3.1167865 = idf(docFreq=580497, maxDocs=4820692)
9.476681 = idf(docFreq=1003, maxDocs=4820692)
9.195494 = idf(docFreq=1329, maxDocs=4820692)
11.576243 = idf(docFreq=122, maxDocs=4820692)
6.3489246 = idf(docFreq=22913, maxDocs=4820692)
12.31089 = idf(docFreq=58, maxDocs=4820692)
13.392695 = idf(docFreq=19, maxDocs=4820692)
11.229373 = idf(docFreq=173, maxDocs=4820692)
12.862067 = idf(docFreq=33, maxDocs=4820692)
0.25 = fieldNorm(doc=199491)
</str></lst><str name="QParser">ExtendedDismaxQParser</str><null
name="altquerystring"/><null name="boostfuncs"/><lst
name="timing"><double name="time">16.0</double><lst
name="prepare"><double name="time">0.0</double><lst
name="org.apache.solr.handler.component.QueryComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.FacetComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.MoreLikeThisComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.HighlightComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.StatsComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.DebugComponent"><double
name="time">0.0</double></lst></lst><lst name="process"><double
name="time">15.0</double><lst
name="org.apache.solr.handler.component.QueryComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.FacetComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.MoreLikeThisComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.HighlightComponent"><double
name="time">8.0</double></lst><lst
name="org.apache.solr.handler.component.StatsComponent"><double
name="time">0.0</double></lst><lst
name="org.apache.solr.handler.component.DebugComponent"><double
name="time">7.0</double></lst></lst></lst></lst>
I hope you can read it:)
Best Regards
Vadim
2012/1/31 Erick Erickson <er...@gmail.com>:
> Seeing the results with &debugQuery=on would help.
>
> No, fq does NOT get translated into q params, it's a
> completely separate mechanism so I'm not quite sure
> what you're seeing.
>
> Best
> Erick
>
> On Tue, Jan 31, 2012 at 8:40 AM, Vadim Kisselmann
> <v....@googlemail.com> wrote:
>> Hi Ahmet,
>>
>> thanks for quick response :)
>> I've also discovered this failure.
>> I wonder that the query themselves works.
>> For example: query = language:de
>> I get results which only have language:de.
>> Also works the fq and i get only the "de"-result in my field "language".
>> I can't understand the behavior. It seems like the fq works, but at
>> the end my fq-params be converted to q-params.
>>
>> Regards
>> Vadim
>>
>>
>>
>> 2012/1/31 Ahmet Arslan <io...@yahoo.com>:
>>>> in calalina.out i can see the following query:
>>>> path=/select/
>>>> params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
>>>> hits=1 status=0 QTime=65
>>>>
>>>> language:de is a filter, and shouldn't be highlighted.
>>>> Do i have a thinking error, or is my query wrong? Or is it
>>>> an edismax problem?
>>>
>>> In your example, language:de is a part of query. Use &fq= instead.
>>> q=(roomba OR irobot)&fq=language:de
>>>
Re: Edismax, Filter Query and Highlighting
Posted by Erick Erickson <er...@gmail.com>.
Seeing the results with &debugQuery=on would help.
No, fq does NOT get translated into q params, it's a
completely separate mechanism so I'm not quite sure
what you're seeing.
Best
Erick
On Tue, Jan 31, 2012 at 8:40 AM, Vadim Kisselmann
<v....@googlemail.com> wrote:
> Hi Ahmet,
>
> thanks for quick response :)
> I've also discovered this failure.
> I wonder that the query themselves works.
> For example: query = language:de
> I get results which only have language:de.
> Also works the fq and i get only the "de"-result in my field "language".
> I can't understand the behavior. It seems like the fq works, but at
> the end my fq-params be converted to q-params.
>
> Regards
> Vadim
>
>
>
> 2012/1/31 Ahmet Arslan <io...@yahoo.com>:
>>> in calalina.out i can see the following query:
>>> path=/select/
>>> params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
>>> hits=1 status=0 QTime=65
>>>
>>> language:de is a filter, and shouldn't be highlighted.
>>> Do i have a thinking error, or is my query wrong? Or is it
>>> an edismax problem?
>>
>> In your example, language:de is a part of query. Use &fq= instead.
>> q=(roomba OR irobot)&fq=language:de
>>
Re: Edismax, Filter Query and Highlighting
Posted by Vadim Kisselmann <v....@googlemail.com>.
Hi Ahmet,
thanks for quick response :)
I've also discovered this failure.
I wonder that the query themselves works.
For example: query = language:de
I get results which only have language:de.
Also works the fq and i get only the "de"-result in my field "language".
I can't understand the behavior. It seems like the fq works, but at
the end my fq-params be converted to q-params.
Regards
Vadim
2012/1/31 Ahmet Arslan <io...@yahoo.com>:
>> in calalina.out i can see the following query:
>> path=/select/
>> params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
>> hits=1 status=0 QTime=65
>>
>> language:de is a filter, and shouldn't be highlighted.
>> Do i have a thinking error, or is my query wrong? Or is it
>> an edismax problem?
>
> In your example, language:de is a part of query. Use &fq= instead.
> q=(roomba OR irobot)&fq=language:de
>
Re: Edismax, Filter Query and Highlighting
Posted by Ahmet Arslan <io...@yahoo.com>.
> in calalina.out i can see the following query:
> path=/select/
> params={hl=true&version=2.2&indent=on&rows=10&start=0&q=(roomba+OR+irobot)+AND+language:de}
> hits=1 status=0 QTime=65
>
> language:de is a filter, and shouldn't be highlighted.
> Do i have a thinking error, or is my query wrong? Or is it
> an edismax problem?
In your example, language:de is a part of query. Use &fq= instead.
q=(roomba OR irobot)&fq=language:de