Hi Karl, So you would write a QueryParser that leveraged the patch to get multiple results/ResponseBuilders etc. and then do some custom magic to return a final result. Ok, I slightly misunderstood the scope of the patch (thought it let the client queries/params decide what the 'magic' is) - but it's still useful and a clever tool!
Thanks, Peter On Fri, Mar 4, 2011 at 6:28 PM, <karl.wri...@nokia.com> wrote: > All that the patch contributes is the infrastructure needed to allow > multiple queries. It’s structured so that the results from one query are > available to construct the query for the next. The patch does not > contribute a multi-query query parser, or means of merging the results into > a final result. > > > > Karl > > > > *From:* ext Peter Sturge [mailto:peter.stu...@gmail.com] > *Sent:* Friday, March 04, 2011 1:04 PM > *To:* dev@lucene.apache.org > *Subject:* Re: [jira] Commented: (SOLR-2026) Need infrastructure support > in Solr for requests that perform multiple sequential queries > > > > Hi Karl, > > Yes, from looking at the conflicts, it looked like trunk changes were > causing the errors - but won't be too difficult to fix these. > > I've got the patch (+tweaks) installed and working, and basic (i.e. non > qt=multiquery) searches are working fine. > What I can't figure out is how to enter in sequential queries from a > browser client (i.e. 'query1', 'query2' etc.). > Yep, understand you can't include proprietary code - but can you show the > query syntax that will shove a couple of sequential queries into the > requestHandler? > Or am I misunderstanding the patch and there's server-side code to write? > > Thanks, > Peter > > > On Fri, Mar 4, 2011 at 5:11 PM, Karl Wright (JIRA) <j...@apache.org> > wrote: > > > [ > https://issues.apache.org/jira/browse/SOLR-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002719#comment-13002719] > > Karl Wright commented on SOLR-2026: > ----------------------------------- > > Lots of stuff has changed in trunk since the patch was posted. I think > you'd have to debug it all over again, and attach a new patch, to bring it > up to date. > > Since this basically should work the same for a single query as does the > current trunk, the first round of testing is just making sure everything > still works as before. If you then change solrconfig.xml to specify > multiple query processing chains, then obviously you need code that can work > with that. I tested it with proprietary Nokia code, so I can't exactly > include that. ;-) > > > > Need infrastructure support in Solr for requests that perform multiple > sequential queries > > > ----------------------------------------------------------------------------------------- > > > > Key: SOLR-2026 > > URL: https://issues.apache.org/jira/browse/SOLR-2026 > > Project: Solr > > Issue Type: New Feature > > Components: SearchComponents - other > > Reporter: Karl Wright > > Priority: Minor > > Fix For: 4.0 > > > > Attachments: SOLR-2026.patch, SOLR-2026.patch > > > > > > Several known cases exist where multiple index searches need to be > performed in order to arrive at the final result. Typically, these have the > constraint that the results from one search query are required in order to > form a subsequent search query. While it is possible to write a custom > QueryComponent or search handler to perform this task, an extension to the > SearchHandler base class would readily permit such query sequences to be > configured using solrconfig.xml. > > I will be therefore writing and attaching a patch tomorrow morning which > supports this extended functionality in a backwards-compatible manner. The > tricky part, which is figuring out how to funnel the output of the previous > search result into the next query, can be readily achieved by use of the > SolrRequestObject.getContext() functionality. The stipulation will > therefore be that the SolrRequestObject's lifetime will be that of the > entire request, which makes complete sense. (The SolrResponseObject's > lifetime will, on the other hand, be limited to a single query, and the last > response so formed will be what gets actually returned by SearchHandler.) > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > > >
