# No reindexing of NumericFieldValues? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 4, 2015, 8:23pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150 "2015-05-04T20:23:12Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Valentin\_Pletzer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/valentin_pletzer/32/105548_2.png) [@Valentin\_Pletzer](https://discuss.elastic.co/u/Valentin_Pletzer)\ **Post date:** [May 4, 2015, 8:23pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/1 "2015-05-04T20:23:12Z")
According to this article [http://shaierera.blogspot.com/2013/09/boosting-documents-in-lucene.html](http://shaierera.blogspot.com/2013/09/boosting-documents-in-lucene.html) Lucene allows for updating NumericFieldValues without reindexing the whole document. The help doc on Partial Updates in Elasticsearch implies otherwise. Can anyone explain how it is solved in Elasticsearch? ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [May 6, 2015, 12:37pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/2 "2015-05-06T12:37:35Z")
Elasticsearch doesn't expose this feature for now. Note that the understanding that even if the document does not need to be reindexed, this feature in Lucene requires doc values for all documents in the same segment to be rewritten. So while this has benefits in certain cases, it definitely has costs too, they are just different. ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [May 6, 2015, 12:39pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/3 "2015-05-06T12:39:18Z")
Something else that I forgot to mention: this works for doc values but not for indexed fields. So you could not search on them, only sort or aggregate. ---
**Author:** ![Valentin\_Pletzer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/valentin_pletzer/32/105548_2.png) [@Valentin\_Pletzer](https://discuss.elastic.co/u/Valentin_Pletzer)\ **Post date:** [May 6, 2015, 1:52pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/4 "2015-05-06T13:52:15Z")
Thanks. I am currently looking for the best way to integrate popularity data into elasticsearch. We would like to use pageview data which is changing constantly (eg daily). Another idea of mine is to use a parent-child-relation in order to move the changing data into another "document". What do you think? Is there any literature/best practise documentation on that topic? ---
**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\ **Post date:** [May 6, 2015, 11:07pm UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/5 "2015-05-06T23:07:13Z")
This is a hard issue. Parent/child could work but it typically makes things much slower too. Also note that parent/child will only work better than regular updates if documents are very large, otherwise it would be better to just use the \_update API. ---
**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:15am UTC](https://discuss.elastic.co/t/no-reindexing-of-numericfieldvalues/150/6 "2017-07-06T00:15:17Z")