On 3/27/2012 11:14 AM, Mark Miller wrote:
On Mar 27, 2012, at 10:51 AM, Shawn Heisey wrote:
On 3/26/2012 6:43 PM, Mark Miller wrote:
It doesn't get thrown because that logic needs to continue - you don't
necessarily want one bad document to stop all the following documents from
being added.
https://issues.apache.org/jira/browse/SOLR-445
This JIRA reflects the slightly different case of wanting better
reporting of *which* document failed in a multi-document packet, it
doesn't specifically address SUSS. But it might serve to give you some
ideas if you tackle this.
On Tue, Mar 27, 2012
On Mar 27, 2012, at 10:51 AM, Shawn Heisey wrote:
> On 3/26/2012 6:43 PM, Mark Miller wrote:
>> It doesn't get thrown because that logic needs to continue - you don't
>> necessarily want one bad document to stop all the following documents from
>> being added. So the exception is sent to that m
On 3/26/2012 6:43 PM, Mark Miller wrote:
It doesn't get thrown because that logic needs to continue - you don't
necessarily want one bad document to stop all the following documents from
being added. So the exception is sent to that method with the idea that you can
override and do what you wo
Like I said, you have to extend the class and override the error method.
Sent from my iPhone
On Mar 27, 2012, at 2:29 AM, Shawn Heisey wrote:
> On 3/26/2012 10:25 PM, Shawn Heisey wrote:
>> The problem is that I currently have no way (that I know of so far) to
>> detect that a problem happene
On 3/26/2012 10:25 PM, Shawn Heisey wrote:
The problem is that I currently have no way (that I know of so far) to
detect that a problem happened. As far as my code is concerned,
everything worked, so it updates my position tracking and those
documents will never be inserted. I have not yet de
On 3/26/2012 6:43 PM, Mark Miller wrote:
It doesn't get thrown because that logic needs to continue - you don't
necessarily want one bad document to stop all the following documents from
being added. So the exception is sent to that method with the idea that you can
override and do what you wo
It doesn't get thrown because that logic needs to continue - you don't
necessarily want one bad document to stop all the following documents from
being added. So the exception is sent to that method with the idea that you can
override and do what you would like. I've written sample code around s
I've been building a new version of my app that keeps our Solr indexes
up to date. I had hoped to use StreamingUpdateSolrServer instead of
CommonsHttpSolrServer for performance reasons, but I have run into a
showstopper problem that has made me revert to CHSS.
I have been relying on exception
