nt Group
> (615) 213-4311
>
>
> -Original Message-
> From: pkeegan01...@gmail.com [mailto:pkeegan01...@gmail.com] On Behalf Of
> Peter Keegan
> Sent: Friday, January 17, 2014 7:51 AM
> To: solr-user@lucene.apache.org
> Subject: Re: How to override rollback behavior in D
.@gmail.com] On Behalf Of Peter
Keegan
Sent: Friday, January 17, 2014 7:51 AM
To: solr-user@lucene.apache.org
Subject: Re: How to override rollback behavior in DIH
Following up on this a bit - my main index is updated by a SolrJ client in
another process. If the DIH fails, the SolrJ client is never
I'm actually doing the 'skip' on every successful call to 'nextRow' with
this trick:
row.put("$externalfield",null); // DocBuilder.addFields will skip fields
starting with '$'
because I'm only creating ExternalFieldFields. However, an error could also
occur in the 'init' call, so exceptions have
Can you try using onError=skip on your entities which use this data source?
It's been some time since I looked at the code so I don't know if this
works with data source. Worth a try I guess.
On Fri, Jan 17, 2014 at 7:20 PM, Peter Keegan wrote:
> Following up on this a bit - my main index is upd
Following up on this a bit - my main index is updated by a SolrJ client in
another process. If the DIH fails, the SolrJ client is never informed of
the index rollback, and any pending updates are lost. For now, I've made
sure that the DIH processor never throws an exception, but this makes it a
bit
I have a custom data import handler that creates an ExternalFileField from
a source that is different from the main index. If the import fails (in my
case, a connection refused in URLDataSource), I don't want to roll back any
uncommitted changes to the main index. However, this seems to be the
defa
