It's possible this may have changed in a recent release, and I don't
know about it, but when I last checked, the only information you could
get out of solrj was a SolrServerException with some very limited info -
basically - an error occurred on the server, and maybe HTTP 400.
When you say you see it in the browser, do you mean in the solr admin
webapp? If so, that's being generated in solr, and not transmitted via
javabin to solrj.
Erick - I don't know if you're (still) following this thread, but this
is an area that could really use some attention, I think, from a
committer. It's relatively straightforward to fix, and will make a
substantial improvement for solrj users. If you're still looking for
tickets to push forward :)
-Mike
On 1/8/2012 4:41 PM, Shawn Heisey wrote:
On 1/6/2012 3:57 PM, Michael Sokolov wrote:
See SOLR-141; there are a few patches - currently all you get back is
a 400 error with no actual information equivalent to what is logged
in the solr exception.
If I can get the HTTP code and the text that's in the error you see in
the browser, that's good enough. I just need to know how to get it.
I didn't see any code in SOLR-141 for how to do this. Having the full
exception would be nice, but not really necessary.
Thanks,
Shawn
