Sorry clicked send to early :-)
with the above additional code the calculation is done by the default
similarity and the behaviour is as expected.
I think this is an issue of the implementation but I didn't find one in
jira. Should I create one?
Cheers
Sascha
On Thu, Feb 25, 2016 at 11:12 PM,
Hi,
I finally found the source of the problem I'm having with the custom
similarity.
The setting:
- Solr 5.4.1
- the SpecialSimilarity extends ClassicSimilarity
- for one field this similarity is configured. Everything else uses
ClassicSimilarity because of
Result:
- most calculation is done by
