[SOLR-4127] Atomic updates used w/o updateLog should throw an error

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.1, 6.0
• Component/s: update
• Assignee: Chris M. Hostetter
• Reporter: Lukas Graf
• Created: 29/Nov/12 23:32
• Updated: 09/May/16 18:54
• Resolved: 11/Dec/12 17:58

Description

The atomic update feature described in SOLR-139 seems to depend on having an <updateLog /> configured in solrconfig.xml.

When used without an update log, the update commands like set or add don't result in an error and the transaction being aborted, but produce garbled documents instead. This is the case for both the XML and JSON formats for the update message.

Example:

I initially created some content like this:

$ curl 'localhost:8983/solr/update?commit=true' -H 'Content-type:application/json' -d '
[{"id":"7cb8a43c","Title":"My original Title", "Creator": "John Doe"}]'

Which resulted in this document:

<doc>
    <str name="id">7cb8a43c</str>
    <str name="Title">My original Title</str>
    <str name="Creator">John Doe</str>
</doc>

Then I attempted to update that document with this statement:

$ curl 'localhost:8983/solr/update?commit=true' -H 'Content-type:application/json' -d '
[{"id":"7cb8a43c","Title":{"set":"My new title"}}]'

Which resulted in this garbled document, with the fields that weren't updated missing:

<doc>
    <str name="id">7cb8a43c</str>
    <str name="Title">{set=My new title}</str>
</doc>

Issue Links

• relates to: SOLR-5977 RunUpdateProcessor: Improve error reporting for "appears to still contain Atomic document update operations"