You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by Apache Wiki <wi...@apache.org> on 2013/04/27 18:42:18 UTC

[Solr Wiki] Update of "Atomic_Updates" by JackKrupansky

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "Atomic_Updates" page has been changed by JackKrupansky:
http://wiki.apache.org/solr/Atomic_Updates?action=diff&rev1=2&rev2=3

  
  = Atomic Updates =
  
- Atomic Updates is a new feature in Solr 4.0 that allows you to update on a field level rather than on a document level (In previous versions). This means that you can update individual fields without having to send the document to Solr with the update fields values. Internally Solr re-adds the document to the index with the updated fields.
+ Atomic Updates is a new feature in Solr 4.0 that allows you to update on a field level rather than on a document level (In previous versions). This means that you can update individual fields without having to send the entire document to Solr with the un-updated fields values. Internally Solr re-adds the document to the index with the updated fields.
  
  <<TableOfContents(2)>>
  
@@ -23, +23 @@

  
  == Stored Values ==
  
- The core functionality of atomicaly updating a document requires that all fields in your SchemaXml must be configured as {{{stored="true"}}} except for fields which are {{{<copyField/>}}} destinations -- which must be configured as {{{stored="false"}}}.  This is because the atomic updates are applied to the document represented by the existing stored field values.
+ The core functionality of atomically updating a document requires that all fields in your SchemaXml must be configured as {{{stored="true"}}} except for fields which are {{{<copyField/>}}} destinations -- which must be configured as {{{stored="false"}}}.  This is because the atomic updates are applied to the document represented by the existing stored field values.
  
  == Update Log ==