[
https://issues.apache.org/jira/browse/SOLR-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895500#action_12895500
]
Karl Wright edited comment on SOLR-2026 at 8/4/10 9:31 PM:
-----------------------------------------------------------
"What if I want to send different data the second time? Or if I want to choose
between two subsequent queries based on the first response?"
I see no reason whatsoever that this proposal would be unable to do precisely
those kinds of things. Indeed, that's the whole point.
I'm not sure what you are bringing in javascript for. Are you talking
server-side javascript, or client-side? If server-side, this sounds like
adding extra wheels whose incremental utility is unclear. If client-side, then
it's completely orthogonal to this proposal.
Reading a bit between the lines, it sounds like you are thinking in terms of
multiple Lucene queries that result from multiple, different request queries.
But that's not the model I'm talking about at all - I'm looking at a single
request query, but multiple Lucene queries, each resulting from execution of a
distinct set of search components on that single request query.
was (Author: [email protected]):
"What if I want to send different data the second time? Or if I want to
choose between two subsequent queries based on the first response?"
I see no reason whatsoever that this proposal would be unable to do precisely
those kinds of things. Indeed, that's the whole point.
I'm not sure what you are bringing in javascript for. Are you talking
server-side javascript, or client-side? If server-side, this sounds like
adding extra wheels whose incremental utility is unclear. If client-side, then
it's completely orthogonal to this proposal.
> 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: Improvement
> Components: SearchComponents - other
> Reporter: Karl Wright
> Attachments: 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
