# Why some boolean settings has two different suffix one is "enable" and another is "enabled"

**URL:** <https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906>\
**Category:** Elasticsearch\
**Created:** [January 20, 2022, 8:05am UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906 "2022-01-20T08:05:01Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![GrandFisher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grandfisher/32/96012_2.png) [@GrandFisher](https://discuss.elastic.co/u/GrandFisher)\
**Post date:** [January 20, 2022, 8:05am UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906/1 "2022-01-20T08:05:01Z")

</div>

I want to know why the class `EnableAllocationDecider` has a setting called `cluster.routing.allocation.enable` which end with "enable", while class `IndicesService` has setting `indices.id_field_data.enabled` which end with "enabled".  
Are there any rules for naming these configurations?

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 25, 2022, 1:01pm UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906/2 "2022-01-25T13:01:05Z")

</div>

That very likely is a design decision from many years ago. Feel free to open a github issue to unify these kind of settings.

---

<div class="post-metadata">

**Author:** ![GrandFisher](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/grandfisher/32/96012_2.png) [@GrandFisher](https://discuss.elastic.co/u/GrandFisher)\
**Post date:** [January 25, 2022, 2:52pm UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906/3 "2022-01-25T14:52:04Z")

</div>

OK， I'll do it. Which one do you think is more reasonable? I prefer to “enable”

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [January 25, 2022, 4:09pm UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906/4 "2022-01-25T16:09:43Z")

</div>

On top of my head I'd say that `enabled` is more common, but feel free to leave that to the development team in the GitHub issue.

---

<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:** [February 22, 2022, 4:10pm UTC](https://discuss.elastic.co/t/why-some-boolean-settings-has-two-different-suffix-one-is-enable-and-another-is-enabled/294906/5 "2022-02-22T16:10:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.