[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830271#action_12830271
]
Mark Miller commented on SOLR-1743:
-----------------------------------
Not quite as bad as I thought - I guess this is setup to work right with
multicore. Wasn't seeing the full picture.
The reason we don't see the error is because the core doesn't load, and
abortOnConfigurationError never gets set to true. We don't handle that setting
correctly with MultiCore - we check it by iterating through all of the cores
that loaded - but a core with a config erorr wouldn't have loaded ... so
abortOnConfigError gets read as false when it should be true.
So we can fix that, but if you *don't* want to abortOnConfiguration error, your
still going to see this confusing message, so we should prob improve on that as
well.
> error reporting is rendering "404 missing core name in path" for all type of
> errors
> -----------------------------------------------------------------------------------
>
> Key: SOLR-1743
> URL: https://issues.apache.org/jira/browse/SOLR-1743
> Project: Solr
> Issue Type: Bug
> Components: Build
> Environment: all
> Reporter: Marcin
> Assignee: Mark Miller
> Fix For: 1.5
>
>
> despite the error in schema syntax or any other type of error you will always
> get:
> "404 missing core name in path" communicate.
> cheers,
> /Marcin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
