Thanks Erik. How do people handle this scenario? Right now the only option I can think of is to replay the entire batch by doing add for every single doc. Then this will give me error for all the docs which got added from the batch.
On Tue, Feb 9, 2016 at 10:57 PM, Erick Erickson <erickerick...@gmail.com> wrote: > This has been a long standing issue, Hoss is doing some current work on it > see: > https://issues.apache.org/jira/browse/SOLR-445 > > But the short form is "no, not yet". > > Best, > Erick > > On Tue, Feb 9, 2016 at 8:19 AM, Debraj Manna <subharaj.ma...@gmail.com> > wrote: > > Hi, > > > > > > > > I have a Document Centric Versioning Constraints added in solr schema:- > > > > <processor class="solr.DocBasedVersionConstraintsProcessorFactory"> > > <bool name="ignoreOldUpdates">false</bool> > > <str name="versionField">doc_version</str> > > </processor> > > > > I am adding multiple documents in solr in a single call using SolrJ 5.2. > > The code fragment looks something like below :- > > > > > > try { > > UpdateResponse resp = solrClient.add(docs.getDocCollection(), > > 500); > > if (resp.getStatus() != 0) { > > throw new Exception(new StringBuilder( > > "Failed to add docs in solr ").append(resp.toString()) > > .toString()); > > } > > } catch (Exception e) { > > logError("Adding docs to solr failed", e); > > } > > > > > > If one of the document is violating the versioning constraints then Solr > is > > returning an exception with error message like "user version is not high > > enough: 1454587156" & the other documents are getting added perfectly. Is > > there a way I can know which document is violating the constraints either > > in Solr logs or from the Update response returned by Solr? > > > > Thanks >
