: If the front application calls Solr with /select but missing q parameter, : Solr returns a stack trace with its response body, while we expect : XML response with an error message (& the stack trace in the XML). : Is it a feature? : : If so, is the front server responsible about checking required params : before requesting to Solr, correct?
generally speaking, clients should allways try to ensure that they only send welformed requests -- the built in RequestHandlers can't function without a "q" param, so i would say yes they should check that they have a value for that param before sending the request to Solr. if you want their to be a default value for the "q" param, you can configure it in the solrconfig.xml. at a broader level, you are correct - the error reporting is not very clean. we are hoping to eventually fix that so the error reporting is more consistent... http://issues.apache.org/jira/browse/SOLR-141 ...in the mean time, i believe query errors are reported using the HTTP status code (if not 200, then an error) and update errors are reported in the XML response body. -Hoss
