But it is still possible to have a RequestHandler (Say BatchRequestHandler ) which can take in multiple queries . say bc.q.count=3 bc.1.q=[(+a +b) ] bc.2.q=[(+a +c)] bc.3.q=[(+a+ d)]
The response may contain several sections <response> <lst name="bc.1.q"> ...output one 1.q goes here </lst> <lst name="bc.2.q"> ...output of 2.q goes here </lst> <lst name="bc.3.q"> .....output of 3.q goes here </lst> </response> The standard SolrJ API's may not be useful but it can be enhanced. --Noble On Sat, Mar 7, 2009 at 1:51 PM, Shalin Shekhar Mangar <shalinman...@gmail.com> wrote: > On Sat, Mar 7, 2009 at 4:06 AM, Ryan McKinley <ryan...@gmail.com> wrote: > >> >>>> No but you can always fire three requests. Writing your own handler which >>>> prints data in a custom format means that you can no longer use existing >>>> solr clients for java/ruby/python etc. >>>> >>> >>> That's not a fair characterization of at least the Ruby client. The >>> NamedList (err, Hash in Ruby) is simply a data structure returned that can >>> be easily navigated. Sure, any client API that expects a certain structure >>> will have issues, but in general no problem in just Hashing it out. >>> >>> >> Also not entirely true for the solrj client. Assuming the response >> includes the standard solr data structures (NamedList, DocList, Doc, etc...) >> the solrj client will parse the response. >> > > Yes, apologies for the wrong characterization. I meant to say that one > cannot use the nice API methods to navigate the results. > > -- > Regards, > Shalin Shekhar Mangar. > -- --Noble Paul
