lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "Atomic_Updates" by ShawnHeisey
Date Tue, 31 May 2016 16:38:36 GMT
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=4&rev2=5

Comment:
More clarity on the fact that copyField destinations must only use data from copyField.

  
  == 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.  There
is another requirement related to copyField destinations:  All data in these fields must originate
from ''ONLY'' copyField sources.
+ 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.  This
means there another requirement related to copyField destinations:  All data in these fields
must originate from ''ONLY'' copyField sources.  If such fields contain some information that
comes from the indexing program and some information that comes from copyField, then the information
which originally came from the indexing program will likely be lost when an atomic update
is made.
  
  == Update Log ==
  

Mime
View raw message