Thanks, this actually replaces the wt parameter (to noop for instance), so prevents me from supporting multiple formats as well. I got it to work though, using null parser in a custom LBHttpSolrServer (current one seems to ignore parser and use binary all the time).
Steve Molloy Content Analytics Lead | R&D Phone: (514) 908-5406 406 Website: www.opentext.com We can't solve problems by using the same kind of thinking we used when we created them. Attributed to Albert Einstein -----Original Message----- From: Chris Hostetter [mailto:[email protected]] Sent: Tuesday, December 04, 2012 8:39 PM To: [email protected] Subject: Re: Solrj question : Believe there are no setParser method on CloudSolrServer? I'm not sure why CloudSolrServer doesn't let you specify the parser ... i would suggest filing a feature request to make that possible. Even assuming you have that, Erick's suggestion isn't quite what you want... : > haven't tried this personally, but try this: : > server.setParser(new XMLResponseParser()); ...because that tells the SolrServer instance to use the XMLResponseParser to parse the data into a QueryResponse. What you want is essentially to write your own ResponesParser that doesn't do any parsing, and just returns a pointer to the the InputStream it's given. Assuming you have that, it may not matter that CloudSolrServer doesn't let you specify a default RequestParser, you *should* be able to just call SolrRequest.setResponseParser() to force your specific parser to be used (but i haven't sanity checked that works with CloudSolrServer) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
