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 CassandraTargett
Date Mon, 01 Aug 2016 21:13:47 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 CassandraTargett:
https://wiki.apache.org/solr/Atomic_Updates?action=diff&rev1=5&rev2=6

Comment:
Add header for content moved to CWIKI

+ {{{#!wiki important
+ This page exists for the Solr Community to share Tips, Tricks, and Advice about 
+ [[https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents#UpdatingPartsofDocuments-AtomicUpdates|Atomic
Updates]].
+ 
+ Reference material previously located on this page has been migrated to the 
+ [[https://cwiki.apache.org/solr/|Official Solr Reference Guide]].
+ If you need help, please consult the Ref Guide for the version of Solr you are using 
+ for the specific details about using [[https://cwiki.apache.org/confluence/display/solr/Updating+Parts+of+Documents#UpdatingPartsofDocuments-AtomicUpdates|this
feature]].
+ 
+ If you'd like to share information about how you use this feature, please [[FrontPage#How_to_edit_this_Wiki|add
it to this page]].
+ /* cwikimigrated */
+ }}}
+ 
+ 
  <!> [[Solr4.0]]
  
  = 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 entire document to Solr with the un-updated fields values.
Internally Solr re-adds the document to the index with the updated fields.
+ Atomic Updates is a feature added 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)>>
  
- = 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
-  * {{{inc}}} – increments a numeric value by a specific amount
- 
- Example syntaxes...
- 
-  * [[UpdateJSON#Solr_4.0_Example | Update JSON Example]]
-  * [[UpdateXmlMessages#Optional_attributes_for_.22field.22 | Update XML Example]]
- 
  = Caveats and Limitations =
- 
- == 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.  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