[
https://issues.apache.org/jira/browse/SOLR-1817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1817:
------------------------------
Attachment: SOLR-1817.patch
Okay, prob done playing for a bit - this patch mostly fixes the issue where
there is an error loading the default core - it will show you the error and
other cores will work.
Main prob with it is that at /solr, instead seeing a list of cores that did
load (like if the error was not with the default core), you see the default
core error.
Getting closer though - need to resolve that, as well as some other cruft -
certain situations still use SolrConfig.severErrors - hopefully just issues
with solr.xml - or anything else higher than a Core level problem - that all
still needs to be checked and fleshed out 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
>
>
> 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.
