[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829747#action_12829747
]
Hoss Man commented on SOLR-1743:
--------------------------------
We definitely shouldn't be generating a "missing core name in path" for
situations like missconfiguration in a single core setup.
In the trunk, things like attempting to load a RequestHandler class that can't
be found correctly result in a "Severe errors in solr configuration." type
message in the browser, which then shows the stack trace of the problem.
However: something as simple as a typoe like this...
{code}
Index: example/solr/conf/schema.xml
===================================================================
--- example/solr/conf/schema.xml (revision 906596)
+++ example/solr/conf/schema.xml (working copy)
@@ -456,7 +456,7 @@
when adding a document.
-->
- <field name="id" type="string" indexed="true" stored="true" required="true"
/>
+ <field name="id" type="asdfasdf" indexed="true" stored="true"
required="true" />
<field name="sku" type="textTight" indexed="true" stored="true"
omitNorms="true"/>
<field name="name" type="textgen" indexed="true" stored="true"/>
<field name="alphaNameSort" type="alphaOnlySort" indexed="true"
stored="false"/>
{code}
...results in http://localhost:8983/solr/admin/ generating the "missing core
name in path" error described, with no other context.
In Solr 1.4, this same type of error would have generated a "Severe errors in
solr configuration." type message (w/ stack trace) so this definitely seems
like a new bug in IndexSchema config error handling introduced in the trunk
since Solr 1.4
> 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
> 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.
