On Tue, Sep 6, 2011 at 6:56 PM, simon wrote:
> If you're batching the documents when you send them to Solr with the #add
> method, you may be out of luck - Solr doesn't do a very good job of
> reporting which document in a batch caused the failure.
>
> If you reverted to CommonsHTTPServer and adde
If you're batching the documents when you send them to Solr with the #add
method, you may be out of luck - Solr doesn't do a very good job of
reporting which document in a batch caused the failure.
If you reverted to CommonsHTTPServer and added a doc at a time there
wouldn't be any ambiguity, but
Hi Mark,
The implementation is logging anyway, we have subclassed
StreamingUpdateSolrServer and used handleError to log, but inspecting the
stack trace in in the handleError method
does not give any clue about the document(s) that failed. We have a solution
that uses Solr as backend for indexing
The default impl logs with slf4j - just setup logging properly and you will see
the results?
Alternatively, you can subclass and impl that method however you'd like.
On Sep 5, 2011, at 6:36 PM, Leonardo Souza wrote:
> Hi,
>
> Inspecting StreamingUpdateSolrServer#handleError i can't see how to
