Are you sure they will wonder? I’d try it without that and see if the simpler
UI is easier to use. Simple almost always wins the A/B test.
You can use the highlighter to see if a field matched a term. Only use explain
if you need all the scores.
wunder
Walter Underwood
wun...@wunderwood.org
Thank you.
The problem is that Endeca just provided this information. The website users
see how each search result matched the query.
For example this is displayed for a hit:
1 Product Result
| Match Criteria: Material, Product Number
The business users will wonder why we cannot provide this
Oh, and something you/they might also find useful to answer the inverse
question “why didn’t it match” is “explainOther”. It’ll tell you how a
particular document was scored whether or not that particular document was in
the result set. IOW it can tell you why a doc scored zero.
Best,
Erick
>
Yes, debug=explain is expensive. Expensive in the sense that I’d never add it
to every query. But if your business users are trying to understand why query X
came back the way it did by examining individual queries, then I wouldn’t worry.
You can easily see how expensive it is in your situation
My concern was that I thought that explain is resource heavy, and was only used
for debugging queries.
-Original Message-
From: Doug Turnbull
Sent: Thursday, May 21, 2020 4:06 PM
To: solr-user@lucene.apache.org
Subject: Re: Why Did It Match?
Is your concern that the Solr explain
Hi all ,
We have documents to type which parent , child, grandchild and each child
document has a reference field to parent doc and grandchild document has
reference fields to child doc and parent doc .
and each document has multiple fields
ex: few fields on parent doc are age , gender , name
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
All,
Ping. Any options for no-downtime TLS reconfiguration?
- -chris
On 4/23/20 11:35, Christopher Schultz wrote:
> All,
>
> Does anyone know if it is possible to reconfigure Solr's TLS
> configuration (specifically, the server key and
Hi!
I've not been able to delve into this issue deeply, but it could be
useful to know that "fragsizeIsMinimum" and "fragAlignRatio" are new
parameters which have behavior changing default values.
Leaving those with their default values makes the comparison between
8.4 and 8.5 like apples to
I also believe this is due to keystore format confusion.
How exactly do you generate your keystore, what is the keystore file named, and
do you specify the SOLR_SSL_KEY_STORE_TYPE env?
Jan
> 28. mai 2020 kl. 04:03 skrev Zheng Lin Edwin Yeo :
>
> Hi Mike,
>
> Thanks for your reply.
>
> Yes, I
I had a client who asked a lot about CDCR a few years ago, but I kept
recommending
aginst it and recommended them to go for Ericks’s alternative (2), since they
anyway
needed to replicate their Oracle DBs in each DC as well. Much cleaner design to
let
each cluster have a local datasource and
10 matches
Mail list logo
