# What does it mean to "store" a field?

**URL:** <https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893>\
**Category:** Elasticsearch\
**Created:** [November 16, 2011, 10:43pm UTC](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893 "2011-11-16T22:43:42Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Prashant\_Pal](https://avatars.discourse-cdn.com/v4/letter/p/b77776/32.png) [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)\
**Post date:** [September 23, 2014, 11:36am UTC](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893/21 "2014-09-23T11:36:30Z")

</div>

Hi Jorg/Nik,

I tried the scenario like one with storing all fields and one without. So what i came across is

-- The size of index is reduced as mentioned in preceding posts as well  
-- Search time for same query is slightly less with not storing the individual field  
-- But here I am getting an issue like I am not able to retrieve the content with highlight if I am using store:No for fields. So how I can overcome this issue without storing the field.

Also its mentioned like : You can even highlight the content from \_source forcefully by adding "force\_source" : true as mentioned in below link. So any Idea how I can achieve that using not storing the fields.

[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-highlighting.html#\_force\_highlighting\_on\_source](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-highlighting.html#_force_highlighting_on_source)

~Prashant

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [September 23, 2014, 1:42pm UTC](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893/22 "2014-09-23T13:42:07Z")

</div>

You must store the field for highlighting.

Jörg

On Tue, Sep 23, 2014 at 1:36 PM, Prashant Agrawal \<  
[prashant.agrawal@paladion.net](mailto:prashant.agrawal@paladion.net)\> wrote:

> Hi Jorg/Nik,
> 
> I tried the scenario like one with storing all fields and one without. So  
> what i came across is
> 
> -- The size of index is reduced as mentioned in preceding posts as well  
> -- Search time for same query is slightly less with not storing the  
> individual field  
> -- But here I am getting an issue like I am not able to retrieve the  
> content  
> with highlight if I am using store:No for fields. So how I can overcome  
> this  
> issue without storing the field.
> 
> Also its mentioned like : You can even highlight the content from \_source  
> forcefully by adding "force\_source" : true as mentioned in below link. So  
> any Idea how I can achieve that using not storing the fields.
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-highlighting.html#_force_highlighting_on_source)
> 
> ~Prashant
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/What-does-it-mean-to-store-a-field-tp3514176p4063906.html](http://elasticsearch-users.115913.n3.nabble.com/What-does-it-mean-to-store-a-field-tp3514176p4063906.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).
> 
> --  
> 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/1411472190705-4063906.post%40n3.nabble.com](https://groups.google.com/d/msgid/elasticsearch/1411472190705-4063906.post%40n3.nabble.com)  
> .  
> 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/CAKdsXoFA3OWZTqDy\_JysqayH6K8JhqfC%2B0yspLvmGbza29mkAQ%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoFA3OWZTqDy_JysqayH6K8JhqfC%2B0yspLvmGbza29mkAQ%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Prashant\_Pal](https://avatars.discourse-cdn.com/v4/letter/p/b77776/32.png) [@Prashant\_Pal](https://discuss.elastic.co/u/Prashant_Pal)\
**Post date:** [September 24, 2014, 9:02am UTC](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893/23 "2014-09-24T09:02:22Z")

</div>

Hi Jorg,

But while exploring the same I came across somethink like mentioned below:

You can even highlight the content from \_source  
forcefully by adding "force\_source" : true as mentioned in below link. So  
any Idea how I can achieve that using not storing the fields.

[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-highlighting.html#\_force\_highlighting\_on\_source](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-highlighting.html#_force_highlighting_on_source)

~Prashant

---

<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, 1:00am UTC](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893/24 "2017-07-06T01:00:18Z")

</div>

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



[Previous page](https://discuss.elastic.co/t/what-does-it-mean-to-store-a-field/5893.md?page=1)
