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
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.
