You're probably thinking about SOLR-445 (yes, 445. This issue has been hanging around for that long)
But that's for much more recent versions than 4.10.3 so without looking at the Solr logs I don't think there's much of a way to tell. The awkward way is, when a batch fails re-submit the docs either in some kind of binary pattern or one at a time until you find the offending doc. Best, Erick On Wed, Nov 16, 2016 at 10:02 AM, Mike Thomsen <mikerthom...@gmail.com> wrote: > We're stuck on Solr 4.10.3 (Cloudera bundle). Is there any way to detect > with SolrJ when a document added to the index violated the schema? All we > see when we look at the stacktrace for the SolrException that comes back is > that it contains messages about an IOException when talking to the solr > nodes. Solr is up and running, and the documents are only invalid because I > added a Java statement to make a field invalid for testing purposes. When I > remove that statement, the indexing happens just fine. > > Any way to do this? I seem to recall that at least in newer versions of > Solr it would tell you more about the specific error. > > Thanks, > > Mike
