I have an update on this, I have identified at least 2 bugs : 1) Real score / Debug score is not aligned When we operate a shard request with purpose '16388' ( GET_TOP_IDS,SET_TERM_STATS) we correctly pass the global collection stats and we calculate the real score.
When we operate a shard request with purpose '320' ( GET_FIELDS,GET_DEBUG ) we don't pass the global collection stats so the debug score calculus and rendering is not the same as the real score. This can be really confusing and not easy to spot. Proposed solution : we pass the global stats for debugging as well 2) Using the ExactStatCache in a solo collection VS multi collection scenario doesn't work really well with caching. Specifically if we first execute the multi collection query, the global stats cached will be the multi collections one, even if we then operate a single collection query. Vice versa applies. Proposed solution : the list of collections involved in the ExactStatsCache should be affecting the hashing ( and consequent caching of the same global stats) I think we should raise 2 separate bugs in the Solr Jira. What do you think ? -- View this message in context: http://lucene.472066.n3.nabble.com/Distributed-IDF-in-inter-collections-distributed-queries-tp4317519p4317531.html Sent from the Solr - User mailing list archive at Nabble.com.
