Hum sorry I think I didn't get your point right! Maybe what you want to do is more like providing a custom similarity for scoring of matches, see http://lucene.apache.org/core/old_versioned_docs/versions/3_5_0/api/core/org/apache/lucene/search/package-summary.html#changingSimilarity
That way you can keep the termPositions (enabling phrase searches) but make the frequency have no impact in scoring by making the tf() method return a constant value (say 1) instead of the real terms' frequencies. Is this what you were looking for ? If so, you'll have to package you're own code into a jar and make that jar accessible to solr, see http://wiki.apache.org/solr/SolrPlugins for how to plug your custom code into Solr. The main drawback of that approach is that it will be activated for all queries and all fields... -- Tanguy 2012/8/7 Tanguy Moal <tanguy.m...@gmail.com> > May be it wasn't clear in my response, sorry! > You can use a different field for searching (qf parameter for dismax) than > the one for highlighting (hl.fl) : > q="a phrase > query"&qf="text_without_termFreqs"&hl=on&hl.fl="text_with_termFreqs". > > Scoring will be based on fq's fields only (i.e. those without termFreqs). > Highlighting will be base on hl.fl's fields only (i.e. those with > termFreqs, > as required by fast vector highlighter) > > Is it any clearer ? :-) > > Best regards, > > Tanguy > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/termFrequncy-off-and-still-use-fastvector-highlighter-tp3998590p3999544.html > Sent from the Solr - User mailing list archive at Nabble.com. >
