Hi - for example, in edismax where the query analyzer is retrieved, you can create your specific analyzer with a customer SynonymsFilter with its own synonyms file. Of course keep a cache of already constructed analyzers.
We also create custom analyzers based on config but with a per-request modification on the fly such as backing config files, or disabling or adding filters on demand. Cache them and reuse, to spare the cost of construction which can be very high in case of large dictionaries or FSTs. Regards, Markus -----Original message----- > From:Hendrik Haddorp <hendrik.hadd...@gmx.net> > Sent: Monday 18th December 2017 10:55 > To: solr-user@lucene.apache.org > Subject: Re: request dependent analyzer > > Hi, how do multiple analyzers help? > > On 18.12.2017 10:25, Markus Jelsma wrote: > > Hi - That is impossible. But you can construct many analyzers instead. > > > > -----Original message----- > >> From:Hendrik Haddorp <hendrik.hadd...@gmx.net> > >> Sent: Monday 18th December 2017 8:35 > >> To: solr-user <solr-user@lucene.apache.org> > >> Subject: request dependent analyzer > >> > >> Hi, > >> > >> currently we use a lot of small collections that all basically have the > >> same schema. This does not scale too well. So we are looking into > >> combining multiple collections into one. We would however like some > >> analyzers to behave slightly differently depending on the logical > >> collection. We would for example like to use different synonyms in the > >> different logical collections. Is there any clean way on how to do that, > >> like somehow access request parameters from an analyzer? > >> > >> regards, > >> Hendrik > >> > >
