[
https://issues.apache.org/jira/browse/SOLR-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-4672.
----------------------------
Resolution: Fixed
Fix Version/s: 5.0
4.3
Assignee: Hoss Man
bq. Hoss Man: I vote you don't worry about it <G>...
done and done!
I spun off SOLR-4688 to let you worry about that (lemme know if you need help)
and committed what was here...
Committed revision 1465749.
Committed revision 1465770.
> requests for cores which had known startup init failures should result in 500
> not 404
> -------------------------------------------------------------------------------------
>
> Key: SOLR-4672
> URL: https://issues.apache.org/jira/browse/SOLR-4672
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 4.3, 5.0
>
> Attachments: SOLR-4672.patch
>
>
> SOLR-3591 added support for tracking if a core failed to init properly, and
> reporting this data back in STATUS request to the CoreAdminHandler so they
> could be displayed in the UI.
> Attempts to use those cores anyway (for queries or updates, etc...) by
> users/clients that may not realize the core failed to init results in 404
> errors because the core doesn't exist, however it should be fairly straight
> forward to intead return a 500 error wrapping the cause of the init failure.
--
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]
