[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12847175#action_12847175
]
Yonik Seeley commented on SOLR-1817:
------------------------------------
bq. I'm starting to think the whole idea of abortOnConfigurationError is a bad
idea ... especially if no one noticed SOLR-1832 before now. Maybe we should
just kill the whole concept, and have SolrCore initialization fail fast and
propogate any type of Exception up to CoreContainer?
Well, we are bumping major version numbers!
abortOnConfigurationError=false seems like a very minor feature to lose. We
could always poll solr-user to see though.
> Fix Solr error reporting to work correctly with multicore
> ---------------------------------------------------------
>
> Key: SOLR-1817
> URL: https://issues.apache.org/jira/browse/SOLR-1817
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Mark Miller
> Priority: Minor
> Fix For: 1.5
>
> Attachments: SOLR-1817.patch, SOLR-1817.patch, SOLR-1817.patch
>
>
> Here is a rough patch that attempts to fix how error reporting works with
> multi-core (not in terms of logs, but what you see on an http request).
> The patch is not done - more to consider and havn't worked with how this
> changes solrconfigs abortOnConfigurationError, but the basics are here.
> If you attempt to access the path of a core that could not load, you are
> shown the errors that kept the core from properly loading.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
