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
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
Hi,
Recently we deployed solr 8.4.1 on a batch of new servers with 2 NUMAs. I
noticed that query latency almost doubled compared to deployment on single
NUMA machines. Not sure what's causing the huge difference. Is there any
tuning to boost the performance on multiple NUMA machines? Any pointer i
Can some one post here any blogs or url where I can get the detailed steps
involved in configuring grafana dashboard for monitoring solr metrics??
Sent from my iPhone
You can refer the below url
https://lucene.apache.org/solr/guide/7_3/monitoring-solr-with-prometheus-and-grafana.html
On Thu, 24 Sep, 2020, 8:25 am yaswanth kumar, wrote:
> Can some one post here any blogs or url where I can get the detailed steps
> involved in configuring grafana dashboard for
