On 7/21/2021 9:51 PM, Satya Nand wrote:
Hi Shawn,
Thank you, I also had my suspicion on the sow parameter. but I can't figure
out why it is acting differently for analyzed type and non-analyzed.
for example, If I give this query to solr 8.7
fq=negativeattribute:(citychennai mcat43120
20mcat43120)&debug=query&fq=mcatid:(43120 26527 43015)
It parses both queries as you can see for mcatid field it is working like
sow is true.
"parsed_filter_queries": [
"negativeattribute:citychennai mcat43120 mcat43120",
"mcatid:43120 mcatid:26527 mcatid:43015"
]
}
That's very odd. I duplicated it on 8.9.0 with an index built from the
default example config:
|"filter_queries":["id:(foo bar baz)"], "parsed_filter_queries":["id:foo
id:bar id:baz"],|
||
|It seems like a bug to me, but someone with a lot more experience on
the query parsers will need to chime in. I also tried it another way
with the same results:|
||
|||"filter_queries":["{!edismax}id:(foo bar baz)"],
"parsed_filter_queries":["+(id:foo id:bar id:baz)"],|
||
I can confirm from analysis checking on the id field (which is set up as
StrField like your mcatid field) that it is probably the query parser
doing the split here. I don't know why it would work differently for
StrField and TextField with the keyword tokenizer. The same thing
happens on the q parameter as well.
|Thanks,|
|Shawn|
||
||||
