Markus, Jack, I think Ahmet nails it pretty nicely: the similarity functions in question are compatible on the index level. So it is not necessary to create a separate search field.
Ahmet, I like your idea. Will take a look, thanks. Rgds, Dmitry On Tue, Dec 15, 2015 at 7:58 PM, Ahmet Arslan <iori...@yahoo.com.invalid> wrote: > > > I wonder what solr-plugin would be best for this functionality. > How about a custom search component, in its prepare method? > > I think we can access (Solr)IndexSearcher inside a SearchComponent. > setSimilarity in the process method should work. > > Ahmet > > > On Tuesday, December 15, 2015 7:43 PM, Ahmet Arslan > <iori...@yahoo.com.INVALID> wrote: > Hi Dmitry, > > I think this is a legitimate request. Majority of the similarities are > compatible index wise. I think the only exception is sweet spot similarity. > > In Lucene, it can be changed on the fly with a new Searcher. It should be > possible to do so in solr. > > Thanks, > Ahmet > > > > > On Tuesday, December 15, 2015 6:08 PM, Jack Krupansky < > jack.krupan...@gmail.com> wrote: > You would need to define an alternate field which copied a base field but > then had the desired alternate similarity, using SchemaSimilarityFactory. > > See: > https://cwiki.apache.org/confluence/display/solr/Other+Schema+Elements > > > -- Jack Krupansky > > > On Tue, Dec 15, 2015 at 10:02 AM, Dmitry Kan <solrexp...@gmail.com> wrote: > > > Hi guys, > > > > Is there a way to alter the similarity class at runtime, with a > parameter? > > > > -- > > Dmitry Kan > > Luke Toolbox: http://github.com/DmitryKey/luke > > Blog: http://dmitrykan.blogspot.com > > Twitter: http://twitter.com/dmitrykan > > SemanticAnalyzer: www.semanticanalyzer.info > > > -- Dmitry Kan Luke Toolbox: http://github.com/DmitryKey/luke Blog: http://dmitrykan.blogspot.com Twitter: http://twitter.com/dmitrykan SemanticAnalyzer: www.semanticanalyzer.info
