[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12843373#action_12843373
]
Hoss Man commented on SOLR-1743:
--------------------------------
bq. Okay, I sat down and thought about what we should do before really reading
through your suggestion - and I came up with practically the exact same thing -
so I think this is what we should attempt.
I know i brought it up here in the issue comments, but I think we should
probably track this type of change in a separate issue as an "Improvement"
for the scope of this issue, let's start by getting a simpler patch commited
that at least restores the behavior from 1.4 -- w/solr.xml you always get
"missing core name" on config error, w/o solr.xml you get good error messages
even if solrconfig.xml can't be parsed. It won't help new users in who start
with the current example from the trunk (since it has a solr.xml) but it will
get things back to where they were for existing users who try upgrading.
As i recall one of the patches already posted does this just fine (i just can't
remember which one) so that part should be fairly straight forward.
> 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
>
>
> 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.
