The approximate amount of work will be very close to what it would take Solr to just index the documents from a client. Actually it puts a little _more_ of a load on Solr. In the case you do an Atomic Update, Solr has to 1> fetch all the stored fields from the index 2> construct a Solr document 3> change the values in the doc based on the atomic update 4> re-index the doc just as though it had received it from a client.
Whereas if you just send the doc from an external client Solr has to 1> de-serialize the doc 2> index it (identical to step 4 above) The sweet spot for Atomic Updates is when you can't easily get the original document from the system-of-record. Best, Erick On Fri, Feb 23, 2018 at 9:02 AM, Uday Jami <udayj...@gmail.com> wrote: > Can you please let me know what will be the performance impact of trying to > update 120Million records in a collection containing 1 billion records. > The collection contains around 30 columns and only one column out of it is > updated as part of atomic update. > Its not a batch update, the 120 Million updates will happen within 24 hours. > > How is the search on the above collection going to get impacted during the > above update process. > > Thanks, > Uday
