On 2/23/2018 2:28 PM, Hodder, Rick wrote:
> Combining everything into one query is what I'd prefer because as you said,
> one would think that with everything in the same query, the score would
> organize everything nicely.
I don't recall writing anything like that. How did you infer that from
riday, February 23, 2018 10:41 AM
To: solr-user@lucene.apache.org
Subject: Re: SOLR Score Range Changed
The difference seems due to the fact that default similarity in solr 7 is
BM25 while it used to be TF-IDF in solr 4. As you realised, BM25 function is
smoother.
You can configure schema.xml t
Hi Shawn,
Thanks for your help - I'm still finding my way in the weeds of SOLR.
Combining everything into one query is what I'd prefer because as you said, one
would think that with everything in the same query, the score would organize
everything nicely.
>>Assuming you're using the default re
The difference seems due to the fact that default similarity in solr 7 is
BM25 while it used to be TF-IDF in solr 4. As you realised, BM25 function
is smoother.
You can configure schema.xml to use ClassicSimilarity, for instance
https://lucene.apache.org/solr/guide/6_6/major-changes-from-solr-5-to-
On 2/22/2018 9:50 AM, Hodder, Rick wrote:
I am migrating from SOLR 4.10.2 to SOLR 7.1.
All seems to be going well, except for one thing: the score that is coming back
for the resulting documents is giving different scores.
The absolute score has no meaning when you change something -- the
in
I would like to stress how important is what Erick explained.
A lot of times people want to use the score to show it to the
users/calculate probability/doing weird calculations.
Score is used to rank results, given a query.
To give a local ordering.
This is the only useful information for the end
Thx for the clarification
Best regards
Am 01.12.2017 18:25 schrieb "Erick Erickson" :
> Sorting certainly ignores scoring, I'm pretty sure it's just not
> calculated in that case.
>
> If your sorting results in multiple documents in the same bin, people
> will combine the primary sort with a seco
Sorting certainly ignores scoring, I'm pretty sure it's just not
calculated in that case.
If your sorting results in multiple documents in the same bin, people
will combine the primary sort with a secondary sort on score, so in
that case the score is definitely calculated, ie "&sort=day asc, score
Or does the Score even get calculated when i sort or Not?
Am 01.12.2017 4:38 nachm. schrieb "Faraz Fallahi" <
faraz.fall...@googlemail.com>:
> Oki but If ID Just make an simple query with a "where Claude" and sort by
> a field i See no sense in calculating a score right?
>
> Am 01.12.2017 16:33 s
Oki but If ID Just make an simple query with a "where Claude" and sort by a
field i See no sense in calculating a score right?
Am 01.12.2017 16:33 schrieb "Aman Tandon" :
> Hi Faraz,
>
> Solr score which you could retrieved by adding in fl parameter could be
> helpful to understand the following:
Hi Faraz,
Solr score which you could retrieved by adding in fl parameter could be
helpful to understand the following:
1) search relevance ranking: how much score solr has given to the top &
second top document, and with debug=true you could better understand what
is causing that score.
2) You c
What problem are you trying to solve?
If you're trying to cut out "bad" results, I might suggest explicitly using
filters that eliminate undesirable search items in terms that are
meaningful to how your users evaluate relevance.
For example, let's say your users only want items that have at least
The ScoresAsPercentages page is not really instructions for how to normalize
scores. It is an explanation of why a score threshold does not do what you want.
Don’t use thresholds. If you want thresholds, you will need a search engine
with a probabilistic model, like Verity K2. Those generally gi
Hi Sara,
You can use funct and frange to achive needed, but note that scores are
not normalized meaning score 8 does not mean it is good match - it is
just best match. There are examples online how to normalize score (e.g.
http://wiki.apache.org/lucene-java/ScoresAsPercentages).
Other approach
Shay this presentation I gave at apachecon and dc solr exchange might
be useful to you:
http://www.slideshare.net/mobile/o19s/hacking-lucene-for-custom-search-results
Sent from my Windows Phone From: Shay Sofer
Sent: 7/16/2014 6:03 AM
To: solr-user@lucene.apache.org
Subject: Solr score manager
How are you storing this information in your documents?
Regards,
Alex
On 16/07/2014 5:03 pm, "Shay Sofer" wrote:
> Hi All,
>
> I need a specific score mechanism.
>
> I would like to sort my results based on customize scoring field.
> scoring for example -
>
>
>
> 1. If this is a new ob
: Not really. The percentage given in other search packages is fairly
: bogus. You have to do a global batch analysis of all of the index to
: get a true scale for relevance.
Exactly...
https://wiki.apache.org/solr/FAQ#Why_Aren.27t_Scores_returned_as_a_percentage.3F_How_Do_I_normalize_Scores.3F
Not really. The percentage given in other search packages is fairly
bogus. You have to do a global batch analysis of all of the index to
get a true scale for relevance.
On Sat, Aug 25, 2012 at 1:38 PM, Ramzi Alqrainy
wrote:
> You are right Mr.Ravish, because this depends on (ranking and search fi
You are right Mr.Ravish, because this depends on (ranking and search fields)
formula, but please allow me to tell you that Solr score can help us to
define this document is relevant or not in some cases.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Score-threshold-r
It will never return no result because its relative to score in previous
result
If score<0.25*last_score then stop
Since score>0 and last score is 0 for initial hit it will not stop
--
View this message in context:
http://lucene.472066.n3.nabble.com/Solr-Score-threshold-reasonably-independent
Commercial solutions often have %age that is meant to signify the quality
of match. Solr has relative score and you cannot tell by just looking at
this value if a result is relevant enough to be in first page or not.
Score depends on "what else is in the index" so not easy to normalize in
the way
Hi,
I think that this totally depends on your requirements and thus applicable
for a user scenario. Score does not have any absolute meaning, it is always
relative to the query. If you want to watch some particular queries and want
to show results with score above previously set threshold, you can
: Perhaps you can solve your usecase by playing with the new eDismax
: "boost" parameter, which multiplies the functions with the other score
: instead of adding.
and FWIW: the "boost" param of the edismax parser is really just syntactic
sugar for using the "BoostQParsre wrapped arround an edi
Perhaps you can solve your usecase by playing with the new eDismax "boost"
parameter, which multiplies the functions with the other score instead of
adding.
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
On 5. nov. 2011, at 01:26,
:To allow better combination of text match & my functions, I want the text
: score to be normalized between 0 & 1. Is there any way I can achieve that
: here?
It is achievable, but it is not usualy meaningful...
https://wiki.apache.org/lucene-java/ScoresAsPercentages
-Hoss
Check the "Need help in understanding output of searcher.explain()
function" thread.
http://mail-archives.apache.org/mod_mbox/lucene-java-user/201008.mbox/%3CAANLkTi=m9a1guhrahpeyqaxhu9gta9fjbnr7-8-zi...@mail.gmail.com%3E
Regards,
Jayendra
On Fri, Feb 25, 2011 at 6:57 AM, Bagesh Sharma wrote:
>
Hi Santhanaraj
Just search for boost on Solr wiki and see if boost feature suffices your
requirement.
As for highlighting, this explains how to implement solr highlighting
http://wiki.apache.org/solr/HighlightingParameters
- neeti
On Wed, Sep 24, 2008 at 10:31 AM, sanraj25 <[EMAIL PROTECTED]> wr
27 matches
Mail list logo
