Thank you so much for your detailed explanation.
Upon further investigation, I’ve tracked down the root of the vulnerability.
{
"type": "jar",
"name": "net.minidev_json-smart",
"version": "1.3.2",
"path":
"/opt/solr-9.5.0/modules/hdfs/lib/hadoop-client-runtime-3.3.
Milkhail,
Thanks for that pointer to test with a simple query. It works perfectly
with lucene query parser, I see qtime drop by 7 times with this param.
With edismax query, it works with certain caveats that "qf" (query fields)
must have only one field and the query must not have boost/bf param
Cool.
Btw can you rerank results with the corresponding boost query?
On Wed, Feb 14, 2024 at 8:46 PM rajani m wrote:
> Milkhail,
>
> Thanks for that pointer to test with a simple query. It works perfectly
> with lucene query parser, I see qtime drop by 7 times with this param.
>
> With edismax
Hi
I'm leaving this for future reference, I still can't pull the image with docker
pull arm64v8/solr however the way I solved it was by using:
docker pull --platform=linux/arm64 solr
Greetings
On Wed, Jan 31, 2024 at 3:27 PM Ricardo Ruiz wrote:
> When I try to pull the image for arm64v8/solr:
@Rahul Surendran facet indeed is where the time
is spent:
"process": {
"time": 1560,
"query": {
"time": 10
},
"facet": {
"time": 1545
},
On Tue, Feb 13, 2024, 6:03 AM Rahul Goswami wrote:
> Can you pass debug=true with y
Thanks everyone for the tips!
@Mikhail
I tried your suggestion and it seems to work. We do not run into the cold
boot long query time for the particular facet query anymore. Had a
follow-up question: Will adding three or four-facet queries have
performance implications for the searcher? I checked t
Yes, rerank works as an alternative, but the rerank only supports one boost
query, correct? If there are multiple boost conditions such as boost by
date, season and popularity, putting all of them into one complex boost
query is a hard problem, rerank by LTR can help. Thank you for that
pointer.
Hello,
Please check inline below.
On Thu, Feb 15, 2024 at 2:11 AM rajani m wrote:
> Yes, rerank works as an alternative, but the rerank only supports one boost
> query, correct? If there are multiple boost conditions such as boost by
> date, season and popularity, putting all of them into one co
On Thu, Feb 15, 2024 at 12:38 AM Arun Sudhir wrote:
> Thanks everyone for the tips!
> @Mikhail
> I tried your suggestion and it seems to work. We do not run into the cold
> boot long query time for the particular facet query anymore. Had a
> follow-up question: Will adding three or four-facet que
