Atomic updates fetch the doc with RealTimeGet, apply the updates to the fetched doc, then reindex. Whether you use atomic updates or send the entire doc to Solr, it has to deleteById then add. The perf difference between the atomic updates and "normal" updates is likely minimal.
Atomic updates are for when you have changes and want to apply them to a document without affecting the other fields. A regular add will replace an existing document completely. AFAIK Solr will let you mix atomic updates with regular field values, but I don't think it's a good idea. Steve On Jul 8, 2014, at 5:30 PM, Bill Au <bill.w...@gmail.com> wrote: > Solr atomic update allows for changing only one or more fields of a > document without having to re-index the entire document. But what about > the case where I am sending in the entire document? In that case the whole > document will be re-indexed anyway, right? So I assume that there will be > no saving. I am actually thinking that there will be a performance penalty > since atomic update requires Solr to first retrieve all the fields first > before updating. > > Bill
