You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2007/04/27 02:05:15 UTC

[jira] Resolved: (SOLR-179) Save me from myself! Abort on configuration errors

     [ https://issues.apache.org/jira/browse/SOLR-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ryan McKinley resolved SOLR-179.
--------------------------------

    Resolution: Fixed

> 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
>         Assigned To: Ryan McKinley
>             Fix For: 1.2
>
>         Attachments: SOLR-179-ConfigurationErrors.patch, SOLR-179-ConfigurationErrors.patch, 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.