[
https://issues.apache.org/jira/browse/SOLR-1743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Miller updated SOLR-1743:
------------------------------
Attachment: SOLR-1743.patch
Well its no surprise that I'm confusing...
But I swear I tested that stupid patch - and yet .. I must not have ...
Here is a patch updated to trunk and with the correct fix.
Was still looking at the abortOnConfig setting in the wrong place - if the
schema couldn't load, an exception *still* caused the setting check to be
skipped -
so setting check has to go in the createCore call, right after the config
object is created.
Swear I'm looking at the darn exception at http://localhost:8983/solr/admin/
right now.
Like I said, this is not a full fix to the issue, but it least puts us back
where we were with single core, and solves half the multi core problem.
> 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
>
>
> 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.
