# Updating index

**URL:** <https://discuss.elastic.co/t/updating-index/4840>\
**Category:** Elasticsearch\
**Created:** [July 12, 2011, 6:34pm UTC](https://discuss.elastic.co/t/updating-index/4840 "2011-07-12T18:34:52Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Slava\_G](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@Slava\_G](https://discuss.elastic.co/u/Slava_G)\
**Post date:** [July 12, 2011, 6:34pm UTC](https://discuss.elastic.co/t/updating-index/4840/1 "2011-07-12T18:34:52Z")

</div>

Hi,  
I have a question regarding the ability to update index, scenario is :  
I have a documents that coming from the user stream (stream could be  
huge).  
In addition to the document but not together with the document  
(document has unique id) , there document tags  
that are coming , but they could be spread across the stream (one to  
come with document and other separately).

Now the question - is it possible to index the document together with  
a first tag and later on to update the index with new tags / fields ?

Thank You and Best regards.

---

<div class="post-metadata">

**Author:** ![ppearcy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ppearcy/32/980_2.png) [@ppearcy](https://discuss.elastic.co/u/ppearcy)\
**Post date:** [July 12, 2011, 11:34pm UTC](https://discuss.elastic.co/t/updating-index/4840/2 "2011-07-12T23:34:12Z")

</div>

Hey,  
I don't think this is directly possible. For example, you can't say  
for a document that has fields A and B, submit an update with only  
field C. You will need to pull the existing doc from the engine,  
update the original source data and resubmit.

Best Regards,  
Paul

On Jul 12, 12:34 pm, slavag [slav...@gmail.com](mailto:slav...@gmail.com) wrote:

> Hi,  
> I have a question regarding the ability to update index, scenario is :  
> I have a documents that coming from the user stream (stream could be  
> huge).  
> In addition to the document but not together with the document  
> (document has unique id) , there document tags  
> that are coming , but they could be spread across the stream (one to  
> come with document and other separately).
> 
> Now the question - is it possible to index the document together with  
> a first tag and later on to update the index with new tags / fields ?
> 
> Thank You and Best regards.

---

<div class="post-metadata">

**Author:** ![Slava\_G](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@Slava\_G](https://discuss.elastic.co/u/Slava_G)\
**Post date:** [July 13, 2011, 8:09pm UTC](https://discuss.elastic.co/t/updating-index/4840/3 "2011-07-13T20:09:11Z")

</div>

10x.  
Sounds not that good solution.

On Jul 13, 2:34 am, Paul [ppea...@gmail.com](mailto:ppea...@gmail.com) wrote:

> Hey,  
> I don't think this is directly possible. For example, you can't say  
> for a document that has fields A and B, submit an update with only  
> field C. You will need to pull the existing doc from the engine,  
> update the original source data and resubmit.
> 
> Best Regards,  
> Paul
> 
> On Jul 12, 12:34 pm, slavag [slav...@gmail.com](mailto:slav...@gmail.com) wrote:
> 
> > Hi,  
> > I have a question regarding the ability to update index, scenario is :  
> > I have a documents that coming from the user stream (stream could be  
> > huge).  
> > In addition to the document but not together with the document  
> > (document has unique id) , there document tags  
> > that are coming , but they could be spread across the stream (one to  
> > come with document and other separately).
> 
> > Now the question - is it possible to index the document together with  
> > a first tag and later on to update the index with new tags / fields ?
> 
> > Thank You and Best regards.

---

<div class="post-metadata">

**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, 4:00am UTC](https://discuss.elastic.co/t/updating-index/4840/4 "2017-07-06T04:00:43Z")

</div>

Closed on July 6, 2017, 4:00am UTC


