# Frequent updates to documents **URL:** \ **Category:** Elasticsearch\ **Created:** [December 12, 2014, 5:23am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231 "2014-12-12T05:23:55Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jinal\_Shah\_2](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jinal\_Shah\_2](https://discuss.elastic.co/u/Jinal_Shah_2)\ **Post date:** [December 12, 2014, 5:23am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231/1 "2014-12-12T05:23:55Z")
Hi, We are using ES 1.0.3. In our application we do frequent updates to the documents and this is causes delete count to increase quickly and frequent merges. Due to Lucene version issues with our application and ES API, we are not able to use the API and we have written a module to interact with ES. For document creation and updates, we use HTTP POST and always send all fields for updates also. Would sending just the updated fields, reduce the delete count? OR Does update to single field also triggers whole document re-indexing? Thanks in advance for your help!! Regards, Jinal Shah -- The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax Media does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax Media does not accept legal responsibility for the contents of this message or attached files. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\ **Post date:** [December 12, 2014, 5:28am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231/2 "2014-12-12T05:28:21Z")
A small change costs as much as a large one. Your best bet is to batch multiple updates for the same document together if possible. Also make sure that your updates actually change something. Sending the exact same document with the same ID still does an update. On Dec 12, 2014 12:24 AM, "Jinal Shah" [jinal.shah@fairfaxmedia.com.au](mailto:jinal.shah@fairfaxmedia.com.au) wrote: > Hi, > > We are using ES 1.0.3. In our application we do frequent updates to the > documents and this is causes delete count to increase quickly and frequent > merges. > > Due to Lucene version issues with our application and ES API, we are not > able to use the API and we have written a module to interact with ES. For > document creation and updates, we use HTTP POST and always send all fields > for updates also. > > Would sending just the updated fields, reduce the delete count? OR > Does update to single field also triggers whole document re-indexing? > > Thanks in advance for your help!! > > Regards, > Jinal Shah > > The information contained in this e-mail message and any accompanying > files is or may be confidential. If you are not the intended recipient, any > use, dissemination, reliance, forwarding, printing or copying of this > e-mail or any attached files is unauthorised. This e-mail is subject to > copyright. No part of it should be reproduced, adapted or communicated > without the written consent of the copyright owner. If you have received > this e-mail in error please advise the sender immediately by return e-mail > or telephone and delete all copies. Fairfax Media does not guarantee the > accuracy or completeness of any information contained in this e-mail or > attached files. Internet communications are not secure, therefore Fairfax > Media does not accept legal responsibility for the contents of this message > or attached files. > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/fcd97638-c934-4d12-8a8e-165b4ae1fdc9%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1EoSpapW9s9R4oW-BVu7f7tmxCh%2B6%3DuL3h2S4WiMb\_Wg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd1EoSpapW9s9R4oW-BVu7f7tmxCh%2B6%3DuL3h2S4WiMb_Wg%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jinal\_Shah\_2](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jinal\_Shah\_2](https://discuss.elastic.co/u/Jinal_Shah_2)\ **Post date:** [December 15, 2014, 5:10am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231/3 "2014-12-15T05:10:52Z")
Thanks for the Nikolas. Users want to search data instantly after the save, so we are unable to use batch updates. It is good to know that even an update in single field means whole document reindex. Thanks, Jinal On Friday, 12 December 2014 16:23:55 UTC+11, Jinal Shah wrote: > Hi, > > We are using ES 1.0.3. In our application we do frequent updates to the > documents and this is causes delete count to increase quickly and frequent > merges. > > Due to Lucene version issues with our application and ES API, we are not > able to use the API and we have written a module to interact with ES. For > document creation and updates, we use HTTP POST and always send all fields > for updates also. > > Would sending just the updated fields, reduce the delete count? OR > Does update to single field also triggers whole document re-indexing? > > Thanks in advance for your help!! > > Regards, > Jinal Shah > > The information contained in this e-mail message and any accompanying > files is or may be confidential. If you are not the intended recipient, any > use, dissemination, reliance, forwarding, printing or copying of this > e-mail or any attached files is unauthorised. This e-mail is subject to > copyright. No part of it should be reproduced, adapted or communicated > without the written consent of the copyright owner. If you have received > this e-mail in error please advise the sender immediately by return e-mail > or telephone and delete all copies. Fairfax Media does not guarantee the > accuracy or completeness of any information contained in this e-mail or > attached files. Internet communications are not secure, therefore Fairfax > Media does not accept legal responsibility for the contents of this message > or attached files. -- The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax Media does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax Media does not accept legal responsibility for the contents of this message or attached files. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f20e4365-eb20-4b0a-be58-4bdddba46cdc%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f20e4365-eb20-4b0a-be58-4bdddba46cdc%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Jinal\_Shah\_2](https://avatars.discourse-cdn.com/v4/letter/j/73ab20/32.png) [@Jinal\_Shah\_2](https://discuss.elastic.co/u/Jinal_Shah_2)\ **Post date:** [December 15, 2014, 5:11am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231/4 "2014-12-15T05:11:39Z")
Thanks for the reply Nikolas. Users want to search data instantly after the save, so we are unable to use batch updates. It is good to know that even an update in single field means whole document reindex. Thanks, Jinal On Friday, 12 December 2014 16:23:55 UTC+11, Jinal Shah wrote: > Hi, > > We are using ES 1.0.3. In our application we do frequent updates to the > documents and this is causes delete count to increase quickly and frequent > merges. > > Due to Lucene version issues with our application and ES API, we are not > able to use the API and we have written a module to interact with ES. For > document creation and updates, we use HTTP POST and always send all fields > for updates also. > > Would sending just the updated fields, reduce the delete count? OR > Does update to single field also triggers whole document re-indexing? > > Thanks in advance for your help!! > > Regards, > Jinal Shah > > The information contained in this e-mail message and any accompanying > files is or may be confidential. If you are not the intended recipient, any > use, dissemination, reliance, forwarding, printing or copying of this > e-mail or any attached files is unauthorised. This e-mail is subject to > copyright. No part of it should be reproduced, adapted or communicated > without the written consent of the copyright owner. If you have received > this e-mail in error please advise the sender immediately by return e-mail > or telephone and delete all copies. Fairfax Media does not guarantee the > accuracy or completeness of any information contained in this e-mail or > attached files. Internet communications are not secure, therefore Fairfax > Media does not accept legal responsibility for the contents of this message > or attached files. -- The information contained in this e-mail message and any accompanying files is or may be confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail is subject to copyright. No part of it should be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. Fairfax Media does not guarantee the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore Fairfax Media does not accept legal responsibility for the contents of this message or attached files. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/ffd2084b-0fb2-4741-a2d5-52e20252fea6%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/ffd2084b-0fb2-4741-a2d5-52e20252fea6%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:43am UTC](https://discuss.elastic.co/t/frequent-updates-to-documents/21231/5 "2017-07-06T00:43:45Z")