[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1743:
---------------------------
Attachment: SOLR-1743.restore14behavior.patch
Ok, I've been doing some more testing...
First off: a lot of my early comments on this issue were inaccurate -- in some
cases I was trying to test the behavior of trunk using a "single core" example
with some errors in the solrconfig.xml, but i was using the "example/solr" dir
on the trunk, and i completly forgot that it has a solr.xml file in it now.
>From what i can tell, the only real difference between the behavior of trunk,
>and the behavior of Solr 1.4 is that: in 1.4 when using legacy single core
>mode (ie: no solr.xml) you would get good error messages if an low level error
>happened that completely prevented the core from loading (ie: schema init
>problem, or xml parsing problem with solrconfig.xml) This is because the
>default behavior of abortOnConfigurationError was "true" for legacy single
>core mode, and that boolean drives SolrDispatchFilter's decision about what
>type of error message to display.
The latest attached patch (SOLR-1743.restore14behavior.patch) should get us
back to the error reporting behavior of Solr 1.4 -- i think we should go ahead
and commit this to the trunk as a temporary fix for the current bug, while we
flesh out improvements to the entire concept of abortOnConfigurationError in
another issue.
> 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
>
> Attachments: SOLR-1743.patch, SOLR-1743.patch, SOLR-1743.patch,
> SOLR-1743.patch, SOLR-1743.patch, SOLR-1743.restore14behavior.patch
>
>
> 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.
