<abortOnConfigurationError> is just for reading the solr
configurations at startup, and it's been removed in recent versions
anyway so it's not surprising that didn't help.
This has been a "feature" of solr for some time, there's no good way
to say "just keep going". There was some work on this with SOLR-445,
but i tdied on the vine.
Wish I had a better answer
Erick
On Thu, May 30, 2013 at 1:03 PM, Iain Lopata
<iain.d.lop...@ameritech.net> wrote:
> I am using Nutch 1.6 and Solr 1.4.1 on Ubuntu in local mode and using
> Nutch's solrindex to index documents into Solr.
>
>
>
> When indexing documents, I hit an occasional document that does not match
> the Solr schema. For example, a document which has two address fields when
> my Solr schema.xml does not specify address as being multi-valued (and I do
> not want it to be). Ideally, I would like this document to be skipped, an
> error written to the log file for later investigation, and the indexing of
> the remainder of the parsed documents to continue. Instead the job fails.
>
>
>
> I have tried setting
> <abortOnConfigurationError>${solr.abortOnConfigurationError:false}</abortOnC
> onfigurationError> in solrconfig.xml and restarting tomcat, but that does
> not seem to make a difference.
>
>
>
> Where else should I be looking?
>
>
>
