Peter: You're still missing the boat a bit here with your boosts. Boosts applied to "fq" clauses are _completely and totally useless_. Don't even bother putting them, the just confuse me ;).
fq clauses are simple binary decisions and do NOT contribute to scoring in any way at all. Way under the covers, the query is evaluated and ancoded in a bitset over the internal Lucene doc IDs. Each doc that matches results in a 1 in the appropriate place.... This bitset is what goes in the filterCache. Which, incidentally, is why the size of each entry is (some overhead) + maxDoc/8..... Anyway, the entire result of the calculations is just this bit, so there's no room for scoring information. Now, putting boosts in the fq clause doesn't change the results, but if you're expecting them to have any effect on the query you'll be disappointed. Best, Erick On Sat, Oct 4, 2014 at 9:17 AM, PeterKerk <petervdk...@hotmail.com> wrote: > Thanks, removing the fq parameters helped :) > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Flexible-search-field-analyser-tokenizer-configuration-tp4161624p4162667.html > Sent from the Solr - User mailing list archive at Nabble.com.
