[
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.patch
Ok, here's my attempt at making sense of this.
As far as i can tell this restores all of the useful behavior that SOlr 1.4 had
with abortOnConfirurationError in single core mode ... some quick multicore
testing makes me think it's improved the error reporting in some situations
there as well, but i'm sure i haven't tried all of the edge cases -- it may
have broken something.
> 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
>
>
> 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.
