Many who use this tool will ask for another feature, so the tool will become an xmas tree laden with odd special-purpose tricks. It makes more sense to just supply a script-based tool.
On Tue, Dec 22, 2009 at 11:06 PM, Noble Paul (JIRA) <j...@apache.org> wrote: > > [ > https://issues.apache.org/jira/browse/SOLR-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793953#action_12793953 > ] > > Noble Paul commented on SOLR-1093: > ---------------------------------- > > a scripting request handler is beyond the scope of this issue. > > > >> 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 >> Fix For: 1.5 >> >> >> 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. > - > You can reply to this email to add a comment to the issue online. > > -- Lance Norskog goks...@gmail.com
