# Changing a system's index mappings (during code contribution)
**URL:** https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736
**Category:** Kibana
**Created:** [April 7, 2019, 8:48pm UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736 "2019-04-07T20:48:04Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@assaf79](https://discuss.elastic.co/u/assaf79)
#### Post date: [April 7, 2019, 8:48pm UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/1 "2019-04-07T20:48:04Z")
Hi,
I'm looking into adding new indexed fields to the _.logstash_ index (adding an is\_enabled field for instance),
what's the best way to update such an index? if there are some examples of upgrading indices when a new version of elastic starts that would be great. (I saw something called Plugin.getIndexMetaDataUpgrader, but didn't see any implementations of this function, not sure if this is the right direction)
Thanks!
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 8, 2019, 3:59am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/2 "2019-04-08T03:59:01Z")
I don't think I understood the question.
What do you cal "code contribution"?
Is it a logstash question or elasticsearch?
---
### Author:  [@assaf79](https://discuss.elastic.co/u/assaf79)
#### Post date: [April 8, 2019, 5:17am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/3 "2019-04-08T05:17:48Z")
We're trying to add the ability to turn off logstash pipelines managed by the kibana api (in x-pack central management feature),
these are stored in the .logstash index in elastic,
which has a strict mapping which prevents the addition of new fields.
these mappings are a part of the elastic code base.
I'm looking for examples of how system indices are upgraded during elastic version upgrades,
to see how you handle the addition of new fields.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 8, 2019, 5:41am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/4 "2019-04-08T05:41:11Z")
Hmmm. Wondering if it's a good idea... See [Logstash Configuration Management API | Kibana User Guide [6.7] | Elastic](https://www.elastic.co/guide/en/kibana/6.7/logstash-configuration-management-api.html)
> Traditionally users would perform this integration by accessing the the `.logstash` index directly. **Do not do this!** The structure of this index is subject to change, which could cause your integration to break.
Why not just setting: [Configuring Centralized Pipeline Management | Logstash Reference [6.7] | Elastic](https://www.elastic.co/guide/en/logstash/6.7/configuring-centralized-pipelines.html#configuration-management-settings)
```auto
xpack.management.enabled: false
```
Which is the default value anyway...
---
### Author:  [@assaf79](https://discuss.elastic.co/u/assaf79)
#### Post date: [April 8, 2019, 5:53am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/5 "2019-04-08T05:53:14Z")
We wanted to see if we could enhance the central management by working on [issue1](https://github.com/elastic/logstash/issues/10559) and [issue2](https://github.com/elastic/logstash/issues/10558)
the first one would allow disabling a pipeline without deleting it, and still allow logstash to have other pipelines managed by the stack.
I've thought of adding a switch in kibana to enable disable a specific pipeline.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [April 8, 2019, 7:20am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/6 "2019-04-08T07:20:10Z")
I moved your question to #kibana
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 6, 2019, 7:20am UTC](https://discuss.elastic.co/t/changing-a-systems-index-mappings-during-code-contribution/175736/7 "2019-05-06T07:20:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.