Hello Ufuk,
You can log slow queries [1].
If you would want to see currently running queries you would have to extend
SearchHandler and build the custom logic yourself. Watch out for SolrCloud
because the main query as well as the per-shard queries can pass through
that same SearchHandler. You
CVE-2020-13956: Apache HttpClient incorrect handling of malformed
authority component in request URIs
Severity: Medium
Vendor:
The Apache Software Foundation
Versions Affected:
Apache HttpClient 4.5.12 and prior
Apache HttpClient 5.0.2 and prior
Description:
Apache HttpClient versions
Hello All,
Is there a way to see currently executing queries in a SolrCloud? Or a general
strategy to detect a query using absurd amount or resources?
We are using Solr for not only simple querying, but running complex streaming
expressions, facets with large data etc. Sometimes, randomly, CPU
Can you post the managed schema and solrconfig content here ?
Do try the solr admin analysis screen
once as well to see the behaviour for this field.
https://lucene.apache.org/solr/guide/7_6/index.html
On Sun, 27 Dec, 2020, 6:54 pm nettadalet, wrote:
> Thank you, that was helpful!
>
> For
Hi,
thank for the comment, but I tried to use both "sow=false" and "saw=true"
and I still get the same result. For query (TITLE_ItemCode_t:KI_7) I still
see:
Solr 4.6: "parsedquery": "PhraseQuery(TITLE_ItemCode_t:\"ki 7\")"
Solr 7.5: "parsedquery":"+(+(TITLE_ItemCode_t:ki7 (+TITLE_ItemCode_t:ki
Hi,
I've encountered another issue that might be related to nested schema.
Not always, but many times atomic updates fails for some shards with the
message "TransactionLog doesn't know how to serialize class
org.apache.lucene.document.LazyDocument$LazyField".
I checked both options:
1. Set
