# Put data direct into \_all field

**URL:** <https://discuss.elastic.co/t/put-data-direct-into--all-field/82686>\
**Category:** Elasticsearch\
**Created:** [April 18, 2017, 9:58am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686 "2017-04-18T09:58:42Z")\
**Posts on this page:** 6\
**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:** [April 18, 2017, 9:58am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/1 "2017-04-18T09:58:42Z")

</div>

Hi,  
I have index (huge one) and seems that big amount of space are wasted just because I have a filed, named documentField (dynamic mapping) that is index but not stored and it's also by default included in \_all field. To change a mapping, will require reindexing and currently it's not an option, so my question is can I put index data directly in \_all field skipping putting it into documentField ?

Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 20, 2017, 8:09am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/2 "2017-04-20T08:09:02Z")

</div>

The `_all` field contains that anyway, so you can skip putting it into the other one.

---

<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:** [April 20, 2017, 8:54am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/3 "2017-04-20T08:54:34Z")

</div>

Thanks,  
I'm wondering how can I skip to put data into other one, this field is defined as analysable and not stored,  
If I'll not put it into it then it'll not be added to \_all as well. And to change the mapping to not analysable will require reindex of all data.

Thanks

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 20, 2017, 9:03am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/4 "2017-04-20T09:03:07Z")

</div>

You will need to reindex old data. If you updated the field for new data then it should be ok.

---

<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:** [April 20, 2017, 9:07am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/5 "2017-04-20T09:07:27Z")

</div>

Thanks,  
Reindexing currently is not an option, it's about 100TB data, so I'm looking for workaround for that issue.

---

<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:** [May 18, 2017, 9:08am UTC](https://discuss.elastic.co/t/put-data-direct-into--all-field/82686/6 "2017-05-18T09:08:22Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.