[
https://issues.apache.org/jira/browse/SOLR-4487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-4487:
---------------------------
Attachment: SOLR-4487.patch
Patch with fix and tests.
holding off on committing just yet because some other HttpSolrServer changes
that just got committed seem to have broken bunch of tests, waiting for things
to return to stead state.
> SolrException usage in solrj client code can't handle all possible http error
> codes returned by servers -- example "413 Request Entity Too Large"
> -------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-4487
> URL: https://issues.apache.org/jira/browse/SOLR-4487
> Project: Solr
> Issue Type: Improvement
> Components: clients - java
> Affects Versions: 4.0
> Reporter: Alexander Dietrich
> Assignee: Hoss Man
> Attachments: SOLR-4487.patch
>
>
> Solr responds to excessively large queries with a 413 status code, but
> HttpSolrServer.request() loses this information when it tries to look up the
> code in SolrException.ErrorCode, resulting in a status code 0 in the thrown
> exception.
> Being able to see this status code would be helpful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
