You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Peter Sturge (JIRA)" <ji...@apache.org> on 2011/03/04 17:40:37 UTC
[jira] Commented: (SOLR-2026) Need infrastructure support in Solr
for requests that perform multiple sequential queries
[ https://issues.apache.org/jira/browse/SOLR-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002701#comment-13002701 ]
Peter Sturge commented on SOLR-2026:
------------------------------------
Hi Karl,
This patch is a really good idea - many thanks for coming up with this!
I've tried applying this on trunk, but I get a few compile errors from the patch, and I'm not quite sure how to use it in a query.
The compile errors have to do with:
SearchHandler.java (~line 267):
ResponseBuilder rb = new ResponseBuilder();
ResponseBuilder doesn't have a no-arg ctor
ResponseBuilder.java (~line 141): (copyFrom())
debug = rb.debug;
There is no 'debug' parameter.
I've fixed these up locally, but as I've only just looked at this, I thought I'd run it by you before patching it up.
There's also an NPE thrown if debugQuery=true (@DebugComponent.java:56)
I haven't been able to build a query that seems to work..
Do you have any example query urls you use for testing?
http://127.0.0.1:9000/solr/select?qt=multiquery&blah&blah etc...
Many thanks!
Peter
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org