Hi I am looking for a way to faster the update of documents.
In my context, the update replaces one of the many existing indexed fields, and keep the others as is. Right now, I am building the whole document, and replacing the existing one by id. I am wondering if **atomic update feature** would faster the process. >From one hand, using this feature would save network because only a small subset of the document would be send from the client to the server. On the other hand, the server will have to collect the values from the disk and reindex them. In addition, this implies to store the values for every fields (I am not storing every fields) and use more space. Also I have read about the ConcurrentUpdateSolrServer class might be an optimized way of updating documents. I am using spark-solr library to deal with solr-cloud. If something exist to faster the process, I would be glad to implement it in that library. Also, I have split the collection over multiple shard, and I admit this faster the update process, but who knows ? Thoughts ? -- nicolas
