[
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
I think i give up.
First off: sorry mark, this comment was way off base...
bq. I'm also wondering if your patch breaks the purpose of
CoreContainer.Initializer.setAbortOnConfigurationError
...digging through the history i realized that this is how Initializer has
always worked: you can set the default behavior for "legacy" single core mode,
but whenever it sees a solr.xml file it overwrites that default value with
"false"
This is fundamentally what's bitch slapping me at the moment ... the attached
patch tries to mimic the historical behavior, and i think i saw it work (but
i'm kinda cross-eeyed right now so i can honestly say you shouldn't take my
word for it -- i wouldn't) but it doesn't really address the fact that since
the example now contains a solr.xml, anybody who starts with the Solr 1.5
example and makes a typo in their solrconfig.xml so that it's not well formed
won't get a useful error message in the browser like they would in 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
> 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.
