> Is it possible to define different Similarity classes for > different fields?
No. See http://search-lucene.com/m/g9cVf23EQO11/ > We have a use case where we are interested in avoid term > frequency (tf) when > our fields are multiValued. May be omitTermFreqAndPositions="true"?
