[
https://issues.apache.org/jira/browse/SOLR-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623589#comment-13623589
]
Erick Erickson commented on SOLR-4672:
--------------------------------------
Hoss Man: I vote you don't worry about it <G>...
I've just written some tests on that very subject as part of SOLR-4663. I took
a look at your tests and I think I can just add a test for the return code ==
500 to the ones that I've already written verifying that the tests return the
message I expect. There's some infrastructure over in TestLazyCores for
creating lazy core defs that I can leverage. Take me about 5 minutes.
Does that work for you?
> 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
> 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]
