You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org> on 2011/04/29 21:26:03 UTC
[jira] [Created] (SOLR-2482) DataImportHandler; reload-config;
response in case of failure & further requests
DataImportHandler; reload-config; response in case of failure & further requests
--------------------------------------------------------------------------------
Key: SOLR-2482
URL: https://issues.apache.org/jira/browse/SOLR-2482
Project: Solr
Issue Type: Improvement
Components: contrib - DataImportHandler, web gui
Reporter: Stefan Matheis (steffkes)
Priority: Minor
Attachments: reload-config-error.html
Reloading while the config-file is valid is completely fine, but if the config is broken - the Response is plain HTML, containing the full stacktrace (see attachment). further requests contain a {{status}} Element with ??DataImportHandler started. Not Initialized. No commands can be run??, but respond with a HTTP-Status 200 OK :/
Would be nice, if:
* the response in case of error could also be xml formatted
* contain the exception message (in my case ??The end-tag for element type "entity" must end with a '>' delimiter.??) in a seperate field
* use a better/correct http-status for the latter mentioned requests, i would suggest {{503 Service Unavailable}}
So we are able to display to error-message to the user, while the config gets broken - and for the further requests we could rely on the http-status and have no need to check the content of the xml-response.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org
[jira] [Updated] (SOLR-2482) DataImportHandler; reload-config;
response in case of failure & further requests
Posted by "Stefan Matheis (steffkes) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-2482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Matheis (steffkes) updated SOLR-2482:
--------------------------------------------
Attachment: reload-config-error.html
> DataImportHandler; reload-config; response in case of failure & further requests
> --------------------------------------------------------------------------------
>
> Key: SOLR-2482
> URL: https://issues.apache.org/jira/browse/SOLR-2482
> Project: Solr
> Issue Type: Improvement
> Components: contrib - DataImportHandler, web gui
> Reporter: Stefan Matheis (steffkes)
> Priority: Minor
> Attachments: reload-config-error.html
>
>
> Reloading while the config-file is valid is completely fine, but if the config is broken - the Response is plain HTML, containing the full stacktrace (see attachment). further requests contain a {{status}} Element with ??DataImportHandler started. Not Initialized. No commands can be run??, but respond with a HTTP-Status 200 OK :/
> Would be nice, if:
> * the response in case of error could also be xml formatted
> * contain the exception message (in my case ??The end-tag for element type "entity" must end with a '>' delimiter.??) in a seperate field
> * use a better/correct http-status for the latter mentioned requests, i would suggest {{503 Service Unavailable}}
> So we are able to display to error-message to the user, while the config gets broken - and for the further requests we could rely on the http-status and have no need to check the content of the xml-response.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org