Yes I would like to get around to implementing that.
You might find out match query parser useful for selecting analyzers at
query time
https://github.com/o19s/match-query-parser
--
Consultant, OpenSource Connections. Contact info at
http://o19s.com/about-us/doug-turnbull/; Free/Busy (http://b
cific filter's parameters.
Regards,
Markus
-Original message-
> From:Stefan Matheis
> Sent: Monday 18th December 2017 23:02
> To: solr-user@lucene.apache.org
> Subject: Re: request dependent analyzer
>
> Hendrik,
>
> this doesn't exactly answer your question,
Hendrik,
this doesn't exactly answer your question, but I do remember reading a
thread on the lucene-dev list which became a jira ticket eventually - not
that long ago.
Doug asked for something that sounds at least a little bit similar to what
you're asking: https://issues.apache.org/jira/browse/
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.
&g
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
Sent: Monday 18th December 2017 8:35
To: solr-user
Subject: request dependent analyzer
Hi
Hi - That is impossible. But you can construct many analyzers instead.
-Original message-
> From:Hendrik Haddorp
> Sent: Monday 18th December 2017 8:35
> To: solr-user
> Subject: request dependent analyzer
>
> Hi,
>
> currently we use a lot of small collec
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 wo
