[
https://issues.apache.org/jira/browse/SOLR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-179:
-------------------------------
Attachment: SOLR-179-ConfigurationErrors.patch
This is using Erik's new system propety substition to make changing
configuraiton for devlopment/production sites easier
<abortOnConfigurationError>${solr.abortOnConfigurationError:true}</abortOnConfigurationError>
> Save me from myself! Abort on configuration errors
> ---------------------------------------------------
>
> Key: SOLR-179
> URL: https://issues.apache.org/jira/browse/SOLR-179
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Fix For: 1.2
>
> Attachments: SOLR-179-ConfigurationErrors.patch
>
>
> When something goes wrong in solr configuration, I want solr to stop working
> and loudly say "something went wrong" This patch adds a collection of severe
> errors to SolrConfig. If abortOnConfigurationError=true and there are
> errors, the SolrDispatchFilter prints out a nice message saying "hey
> something went wrong!"
> The specific things that were hidden in error files that will now give
> dramatic error are:
> * unknown class for RequestHandler/ResponseWriter
> * any exception throw during handler/writer init()
> If you want to disable this behavior (perhaps for a production environment)
> you need to add:
> <abortOnConfigurationError>false</abortOnConfigurationError>
> to solrconfig.xml
> for more discussion, see:
> http://www.nabble.com/merely-a-suggestion%3A-schema.xml-validator-or-better-schema-validation-logging-tf3331929.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
