lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Graf (JIRA)" <>
Subject [jira] [Created] (SOLR-4127) Atomic updates used w/o updateLog should throw an error
Date Thu, 29 Nov 2012 23:32:58 GMT
Lukas Graf created SOLR-4127:

             Summary: Atomic updates used w/o updateLog should throw an error
                 Key: SOLR-4127
             Project: Solr
          Issue Type: Bug
          Components: update
    Affects Versions: 4.0
            Reporter: Lukas Graf

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.


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:

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

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:

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

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message