[ https://issues.apache.org/jira/browse/SOLR-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986584#action_12986584 ]
Grant Ingersoll commented on SOLR-445: -------------------------------------- Oh, one other thing. You don't need to produce a 3.x patch. We can just do an SVN merge. > XmlUpdateRequestHandler bad documents mid batch aborts rest of batch > -------------------------------------------------------------------- > > Key: SOLR-445 > URL: https://issues.apache.org/jira/browse/SOLR-445 > Project: Solr > Issue Type: Bug > Components: update > Affects Versions: 1.3 > Reporter: Will Johnson > Assignee: Grant Ingersoll > Fix For: Next > > Attachments: SOLR-445-3_x.patch, SOLR-445.patch, SOLR-445.patch, > SOLR-445.patch, solr-445.xml, SOLR-445_3x.patch > > > Has anyone run into the problem of handling bad documents / failures mid > batch. Ie: > <add> > <doc> > <field name="id">1</field> > </doc> > <doc> > <field name="id">2</field> > <field name="myDateField">I_AM_A_BAD_DATE</field> > </doc> > <doc> > <field name="id">3</field> > </doc> > </add> > Right now solr adds the first doc and then aborts. It would seem like it > should either fail the entire batch or log a message/return a code and then > continue on to add doc 3. Option 1 would seem to be much harder to > accomplish and possibly require more memory while Option 2 would require more > information to come back from the API. I'm about to dig into this but I > thought I'd ask to see if anyone had any suggestions, thoughts or comments. > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org