Thanks, this is helpful. I agree. q.op param should not affect fq
parameter. I think this is a feature and not a bug.
On Wed, Sep 23, 2020 at 4:39 PM Erik Hatcher wrote:
> In 6.3 it did that? It shouldn't have. q and fq shouldn't share
> parameters. fq's themselves shouldn't, IMO, have globa
In 6.3 it did that? It shouldn't have. q and fq shouldn't share parameters.
fq's themselves shouldn't, IMO, have global defaults. fq's need to be stable
and often uniquely specified kinds of constraining query parsers
({!terms/term/field,etc}) or rely on basic Lucene query parser syntax and
Is there a way to set default operator as AND for fq parameter in Solr
8.5.2 now?
On Tue, Sep 22, 2020 at 7:44 PM gnandre wrote:
> In 6.3, q.op param used to affect q as well fq param behavior. E.g. if
> q.op is set to AND and fq is set to id:(1 2 3), no results will show up but
> if it is set t
