That implies that you’re using two different queryParsers, one for the “q”
portion and one for the “fq” portion. My guess is that you have solrconfig
/select or /query configured to use (e)dismax but your fq clause is being
parsed by, the LuceneQueryParser.
You can specify the parser via local
Thanks Erick for the clarification. How does the ps work for fq? I
configured ps=4 for q, it doesn't apply to fq though. For phrase queries in
fq seems ps=0 is used. Is there a way to config it for fq also?
Best,
Wei
On Tue, Jun 25, 2019 at 9:51 AM Erick Erickson
wrote:
> q and fq do _exactly
q and fq do _exactly_ the same thing in terms of query parsing, subject to all
the same conditions.
There are two things that apply to fq clauses that have nothing to do with the
query _parsing_.
1> there is no scoring, so it’s cheaper from that perspective
2> the results are cached in a bitmap
Thanks Shawn! I didn't notice the asterisks are created during copy/paste,
one lesson learned :)
Does that mean when fq is applied to text fields, it is doing text match
in the field just like q in a query field? While for string fields, it is
exact match.
If it is a phrase query, what are the v
On 6/24/2019 5:37 PM, Wei wrote:
I'm assuming that the asterisks here are for emphasis, that they are not
actually present. This can be very confusing. It is far better to
relay the precise information and not try to emphasize anything.
For query q=*:*&fq=description:”ice cream”, the f
Hi,
I have always been using solr fq on string fields. Recently I need to apply
fq on one text field defined as follows:
For query q=*:*&fq=description:”ice cream”, the filter query returns
matches for “ice cream b
