: On trunk, you can add the "debug.explain.structured=true" param which will
: cause the explanation messages to be returned as structured data.
backported to 3x for inclusion in 3.2...
https://issues.apache.org/jira/browse/SOLR-1915
-Hoss
: I stumbled upon the 'Explain' function yesterday though it returns a crowded
: message using debug in SOLR admin. Is there another method or interface
: which returns more or cleaner info?
On trunk, you can add the "debug.explain.structured=true" param which will
cause the explanation messages
On Fri, May 20, 2011 at 2:46 PM, Doron Cohen wrote:
> I stumbled upon the 'Explain' function yesterday though it returns a crowded
>> message using debug in SOLR admin. Is there another method or interface
>> which returns more or cleaner info?
>>
>
> I am not familiar with the use of Solr for thi
Hi Rich,
SeetSpotSimilarity looks promising. Does it not favor shorter docs by not
> normalizing or does it make some attempt to standardized.
>
> > - using e.g. SeetSpotSimilarity which do not favor shorter documents.
>
SweetSpotSimilarity (I misspelled it previously) defines a range of lengths
Bingo. That appears to be the essence of the problem, which makes sense
given TF/IDF.
I stumbled upon the 'Explain' function yesterday though it returns a crowded
message using debug in SOLR admin. Is there another method or interface
which returns more or cleaner info?
I feel uncomfortable with
Hi Rich,
If I understand correctly you are concerned that short documents are
preferred too much over long ones, is this really the case?
It would help to understand what goes on to look at the Explanation of the
score for say two result documents - one that you think is ranked too low,
and one tha
Thanks Paul,
I do not know what duplicates are in this case and it is the denominator of
the TF that bothers me more than the numerator of the TF (if that is in fact
what you are suggesting).
What have been the effects of ignoring the IDF? When is it appropriate. It
would seem that by doing so ra
Richard,
in SOLR at least there's an analyzer that avoids duplicates.
I think that would solve it.
There's also somewhere the option to ignore IDF (in similarity? in solrconfig?).
paul
Le 18 mai 2011 à 21:30, Rich Heimann a écrit :
> Hello all,
>
> This is my first time on the list and my fir
Hello all,
This is my first time on the list and my first question...forgive me it this
has been hacked out in the past.
We have set up Lucene/Solr and are getting somewhat spurious results. It
appears to be a result of heterogeneous document sizes. In other words, the
top results are sometimes (
