Hi Erik,
Thanks for your reply. My particular use case is this: 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 query request that comes in. I thought an event handler might be good for auditing (because it could ideally do more than just /select), but the wiki states this doesn't support all operations (like queries). Am I wrong about this? Maybe eventHandlers do more now? Ideally, I'd like to keep the auditing plugin sef-contained, as I think a secure auditing plugin (whether a QParser or something else) would make a good contribution module for Solr. Being able to track what has happened on a Solr instance in a non-repudiated fashion would be [hopefully] useful for others as well (e.g. if you're storing/accessing secure documents and need to know every time someone accesses something). I know there is some logging that tracks requests etc., but log files are difficult to secure in a forensically-legal way. Maybe whatever generates the log entries can be plugged into so that secure, 'tamper-proof' audit trails can be generated? This is somewhat tied to some sort of document-level security, since auditing isn't much use without a user to go with it - but that's a different thread... Is there a better way to track Solr activity? It would be great to have one plugin that could audit not just queries, but also [user-initiated] updates, deletes, server restarts and config changes (although these last two might need to be outside of Solr). Can eventHandler do this? Thanks, Peter > 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.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? > > Erik > > > On Mar 30, 2010, at 10:52 AM, Peter Sturge wrote: > > > 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: > > <str name="defType">qpluginhandler_1</str> then: > > <str name="defType">qpluginhandler_2</str> and finally: > > <str name="defType">qpluginhandler_N</str> > > > > where qpluginhandler_X is some defined QParserPlugin instance. > > > > Is this possible? > > > > Many thanks, > > Peter > _________________________________________________________________ Tell us your greatest, weirdest and funniest Hotmail stories http://clk.atdmt.com/UKM/go/195013117/direct/01/
