# Warmers vs eager field data loading
**URL:** https://discuss.elastic.co/t/warmers-vs-eager-field-data-loading/17565
**Category:** Elasticsearch
**Created:** [May 16, 2014, 7:20pm UTC](https://discuss.elastic.co/t/warmers-vs-eager-field-data-loading/17565 "2014-05-16T19:20:18Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@slushi](https://discuss.elastic.co/u/slushi)
#### Post date: [May 16, 2014, 7:20pm UTC](https://discuss.elastic.co/t/warmers-vs-eager-field-data-loading/17565/1 "2014-05-16T19:20:18Z")
I noticed the warmers documentation mentioned that it's often used for
fields involved in sorting/faceting. My understanding is this is because
those operations require the entire field loaded in the field data cache.
In this case why not set the fielddata.loading property to "eager" in the
field mapping? Wouldn't this accomplish the same thing? Also in what
situation does eager\_global\_ordinals loading option provide benefits?
Thanks!
[http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/fielddata-formats.html#\_fielddata\_loading](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/fielddata-formats.html#_fielddata_loading)
--
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/2afc2ade-dbbc-40e8-bf4c-9143f5de0f54%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2afc2ade-dbbc-40e8-bf4c-9143f5de0f54%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 1:28am UTC](https://discuss.elastic.co/t/warmers-vs-eager-field-data-loading/17565/2 "2017-07-06T01:28:48Z")