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 "Hoss Man (JIRA)" <ji...@apache.org> on 2010/03/19 01:30:30 UTC
[jira] Created: (SOLR-1832) abortOnConfigurationError=false no
longer works for most plugin types
abortOnConfigurationError=false no longer works for most plugin types
---------------------------------------------------------------------
Key: SOLR-1832
URL: https://issues.apache.org/jira/browse/SOLR-1832
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Hoss Man
In 1.4 setting the "abortOnConfigurationError" config option to "false" only affects RequestHandlers and schema related classes (ie: FieldType and Token*Factories).
ValueSourceParsers, QParserPlugins, and ResposneWriters which fail to initalize properly in Solr 1.4 will cause the entire SolrCore to fail to initialize. This changed from previous version: In Solr 1.3 a failure to init any of these types of plugins when abortOnConfigurationError=false would result in errors being logged on init, but the SolrCore itself would still work and only attempts to use those plugins would result in an error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1832) abortOnConfigurationError=false no
longer works for most plugin types
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847170#action_12847170 ]
Hoss Man commented on SOLR-1832:
--------------------------------
This seems to be a result of switching away from the (Map|NamedList)PluginLoader classses when the "PluginInfo" API was added. The PluginLoaders would loop over multiple plugins recording any errors in SolrCOnfig.severErrors but then proceeding -- SolrCore.initPlugins on the other hand fails fast.
> abortOnConfigurationError=false no longer works for most plugin types
> ---------------------------------------------------------------------
>
> Key: SOLR-1832
> URL: https://issues.apache.org/jira/browse/SOLR-1832
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Hoss Man
>
> In 1.4 setting the "abortOnConfigurationError" config option to "false" only affects RequestHandlers and schema related classes (ie: FieldType and Token*Factories).
> ValueSourceParsers, QParserPlugins, and ResposneWriters which fail to initalize properly in Solr 1.4 will cause the entire SolrCore to fail to initialize. This changed from previous version: In Solr 1.3 a failure to init any of these types of plugins when abortOnConfigurationError=false would result in errors being logged on init, but the SolrCore itself would still work and only attempts to use those plugins would result in an error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1832) abortOnConfigurationError=false no
longer works for most plugin types
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-1832.
----------------------------
Resolution: Won't Fix
> abortOnConfigurationError=false no longer works for most plugin types
> ---------------------------------------------------------------------
>
> Key: SOLR-1832
> URL: https://issues.apache.org/jira/browse/SOLR-1832
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Hoss Man
>
> In 1.4 setting the "abortOnConfigurationError" config option to "false" only affects RequestHandlers and schema related classes (ie: FieldType and Token*Factories).
> ValueSourceParsers, QParserPlugins, and ResposneWriters which fail to initalize properly in Solr 1.4 will cause the entire SolrCore to fail to initialize. This changed from previous version: In Solr 1.3 a failure to init any of these types of plugins when abortOnConfigurationError=false would result in errors being logged on init, but the SolrCore itself would still work and only attempts to use those plugins would result in an error.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.