Ahh, SearchComponent, that sounds like the one. I'll have a go with that
and see how I get on. Hooking into log4j might be an option also.
Many thanks for pointing out the right direction.
Peter
On Mar 30, 2010 9:54pm, Erik Hatcher wrote:
On Mar 30, 2010, at 2:43 PM, Peter S wrote:
I h
On Mar 30, 2010, at 2:43 PM, Peter S wrote:
I have an existing QParserPlugin subclass that does some tagging
functionality (kind of a group alias thing). This is currently
registered with the default queryHandler.
I want to add another, quite separate plugin that writes an audit of
every
> From: erik.hatc...@gmail.com
> To: solr-user@lucene.apache.org
> Subject: Re: Multiple QParserPlugins, Single RequestHandler
> Date: Tue, 30 Mar 2010 14:06:28 -0400
>
> No, not quite like that, but you can nest various query parser
> plugins. See
> http://www.lucidimag
No, not quite like that, but you can nest various query parser
plugins. See http://www.lucidimagination.com/blog/2009/03/31/nested-queries-in-solr/
Or perhaps write a composite query parser plugin that runs through the
chain of others as you wish.
I'm curious, what's the use case?
Hi Solr Expoerts,
Is it possible to 'chain' multiple QParserPlugins from a single
RequestHandler?
e.g. when a query request comes in for the default standard requestHandler,
it sends the query request to:
qpluginhandler_1 then:
qpluginhandler_2 and finally:
qpluginhandler
