# Best practices for template mapping in 2.x

**URL:** <https://discuss.elastic.co/t/best-practices-for-template-mapping-in-2-x/33104>\
**Category:** Elasticsearch\
**Created:** [October 27, 2015, 8:05pm UTC](https://discuss.elastic.co/t/best-practices-for-template-mapping-in-2-x/33104 "2015-10-27T20:05:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)\
**Post date:** [October 27, 2015, 8:05pm UTC](https://discuss.elastic.co/t/best-practices-for-template-mapping-in-2-x/33104/1 "2015-10-27T20:05:17Z")

</div>

Since fields can't differ between types in ES 2.0, should I define everything in the _default_ template mapping to ensure consistency? Assuming I end up with 100 fields across all types in an index, will that have a noticeable impact? Thanks!

---

<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 5, 2017, 11:42pm UTC](https://discuss.elastic.co/t/best-practices-for-template-mapping-in-2-x/33104/2 "2017-07-05T23:42:21Z")

</div>

Closed on July 5, 2017, 11:42pm UTC