[Solr Wiki] Update of "Atomic_Updates" by ShawnHeisey

[Apache Wiki <wi...@apache.org>]

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 ShawnHeisey:
https://wiki.apache.org/solr/Atomic_Updates?action=diff&rev1=3&rev2=4

Comment:
added note about copyField destinations *only* being populated by copyField sources.

  = Available Modifiers =
  
   * {{{set}}} – sets or replaces a particular value, or remove the value if {{{null}}} is specified as the new value. <!> Note: In the case of multi-valued fields if {{{null}}} is specified on {{{set}}} all the values in the field are removed. See [[https://issues.apache.org/jira/browse/SOLR-3862|SOLR-3862]]
-  * {{{add}}} – adds an additional value to a multi-valued field 
+  * {{{add}}} – adds an additional value to a multi-valued field
   * {{{inc}}} – increments a numeric value by a specific amount
  
  Example syntaxes...
@@ -23, +23 @@

  
  == Stored 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.
+ 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.  There is another requirement related to copyField destinations:  All data in these fields must originate from ''ONLY'' copyField sources.
  
  == Update Log ==