[
https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620283#comment-13620283
]
David Smiley commented on SOLR-1093:
------------------------------------
-1 If this issue is strictly about a feature in which a batch of queries are
fully known at the time of submission, then I don't think this should be
accepted for inclusion in Solr; sorry. Simply submit them in parallel.
Instead, I am highly in favor of a scripting request handler in which a script
runs that submits the searches to Solr (in-VM) and can react to the results of
one request before making another that is formulated dynamically, and can
assemble the response data, potentially reducing both the latency and data that
would move over the wire if this feature didn't exist. And if you *really*
were bent on submitting a batch of queries that are returned in a batch, then
you could implement that with the script.
> A RequestHandler to run multiple queries in a batch
> ---------------------------------------------------
>
> Key: SOLR-1093
> URL: https://issues.apache.org/jira/browse/SOLR-1093
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Noble Paul
> Assignee: Simon Willnauer
> Attachments: SOLR-1093.patch
>
>
> It is a common requirement that a single page requires to fire multiple
> queries .In cases where these queries are independent of each other. If there
> is a handler which can take in multiple queries , run them in paralll and
> send the response as one big chunk it would be useful
> Let us say the handler is MultiRequestHandler
> {code}
> <requestHandler name="/multi" class="solr.MultiRequestHandler"/>
> {code}
> h2.Query Syntax
> The request must specify the no:of queries as count=n
> Each request parameter must be prefixed with a number which denotes the query
> index.optionally ,it may can also specify the handler name.
> example
> {code}
> /multi?count=2&1.handler=/select&1.q=a:b&2.handler=/select&2.q=a:c
> {code}
> default handler can be '/select' so the equivalent can be
> {code}
> /multi?count=2&1.q=a:b&2.q=a:c
> {code}
> h2.The response
> The response will be a List<NamedList> where each NamedList will be a
> response to a query.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
