# Why "Config mappings"

**URL:** <https://discuss.elastic.co/t/why-config-mappings/62551>\
**Category:** Elasticsearch\
**Created:** [October 8, 2016, 7:56am UTC](https://discuss.elastic.co/t/why-config-mappings/62551 "2016-10-08T07:56:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arsenepark](https://avatars.discourse-cdn.com/v4/letter/a/d07c76/32.png) [@arsenepark](https://discuss.elastic.co/u/arsenepark)\
**Post date:** [October 8, 2016, 7:56am UTC](https://discuss.elastic.co/t/why-config-mappings/62551/1 "2016-10-08T07:56:40Z")

</div>

hi, there

"[Config mappings](https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping-conf-mappings.html)" is removed? why?

Dennis

---

<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:** [October 8, 2016, 8:59am UTC](https://discuss.elastic.co/t/why-config-mappings/62551/2 "2016-10-08T08:59:01Z")

</div>

It was a security risk.  
Things could drift, with different files on different nodes.  
Plus you had to restart a node to get it to re-read the files.

APIs are dynamic and centralised.

---

<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, 10:13pm UTC](https://discuss.elastic.co/t/why-config-mappings/62551/3 "2017-07-05T22:13:55Z")

</div>

Closed on July 5, 2017, 10:13pm UTC