Hi, if you add to the request the param : debugQuery=on you will see what happens under the hood and understand how the score is assigned.
If you are new to the Lucene Similarity that Solr version uses ( BM25[1]) you can paste here the debug score response and we can briefly explain it to you the first time. First of all we are not even sure if the content field is actually used for scoring in your case, if it is and it is alone used, it may be related to the field length ( But it would be suspicious as they are quite similar in length in your example). Are you sorting by score for any reason ? It's been a while I have not checked but I doubt you get any benefit from the default ( which rank by score). So I recommend you to send here the debug response and then possibly your select request handler config. Cheers ----- --------------- Alessandro Benedetti Search Consultant, R&D Software Engineer, Director Sease Ltd. - www.sease.io -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
