# When to multi\_field **URL:** \ **Category:** Elasticsearch\ **Created:** [August 27, 2014, 6:02pm UTC](https://discuss.elastic.co/t/when-to-multi-field/19500 "2014-08-27T18:02:25Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![gek8365](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gek8365/32/1314_2.png) [@gek8365](https://discuss.elastic.co/u/gek8365)\ **Post date:** [August 27, 2014, 6:02pm UTC](https://discuss.elastic.co/t/when-to-multi-field/19500/1 "2014-08-27T18:02:25Z")
Greetings, I am somewhat new to elasticsearch and I am trying to understand the implications of multi\_fields in terms of performance/memory consumption. I see from the documents that multi\_fields are useful when you want to analyze field data in different ways. What I do not see is any discussion on how expensive it is to have these additional "fields." I realize that this is a very glib question, which is due in large to my ignorance, so any advice or links to documents that might have some information on this would be very useful and I would be grateful. Thanks in advance. -- 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/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [August 27, 2014, 6:14pm UTC](https://discuss.elastic.co/t/when-to-multi-field/19500/2 "2014-08-27T18:14:03Z")
The standard use case for a multi-field is when a field needs to be both analyzed (for searching) and not analyzed (for aggregating/sorting). In this case, there really is no workaround, so a multi-field is essential. In the different analyzer case, it gets more complicated. How much can you get away with with just one field? How important is query precision compared to storage? In general, more fields are needed because they are truly needed. The upcoming Elasticsearch book has a good chapter on languages, which is one use case in which multi fields are used. The pitfalls of mixing languages section is what you might encounter when attempting to use fewer fields. > **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)** > > Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today. Cheers, Ivan On Wed, Aug 27, 2014 at 11:02 AM, gek8365 [glenn.kidd@gmail.com](mailto:glenn.kidd@gmail.com) wrote: > Greetings, > > I am somewhat new to elasticsearch and I am trying to understand the > implications of multi\_fields in terms of performance/memory consumption. I > see from the documents that multi\_fields are useful when you want to > analyze field data in different ways. What I do not see is any discussion > on how expensive it is to have these additional "fields." I realize that > this is a very glib question, which is due in large to my ignorance, so any > advice or links to documents that might have some information on this would > be very useful and I would be grateful. Thanks in advance. > > -- > 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/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/d05347a1-abf1-401e-bd48-487bb2162c32%40googlegroups.com?utm_medium=email&utm_source=footer) > . > 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/CALY%3DcQCVphM-x7a1MUDgbM7zSX7Y9po7m8Ne5tguSMvz%2BtTt6g%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQCVphM-x7a1MUDgbM7zSX7Y9po7m8Ne5tguSMvz%2BtTt6g%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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:05am UTC](https://discuss.elastic.co/t/when-to-multi-field/19500/3 "2017-07-06T01:05:58Z")