# Mapping conflict!

**URL:** https://discuss.elastic.co/t/mapping-conflict/40248
**Category:** Elasticsearch
**Created:** [January 27, 2016, 2:45pm UTC](https://discuss.elastic.co/t/mapping-conflict/40248 "2016-01-27T14:45:28Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![gildor7](https://avatars.discourse-cdn.com/v4/letter/g/cc9497/32.png) [@gildor7](https://discuss.elastic.co/u/gildor7)
#### Post date: [January 29, 2016, 11:34am UTC](https://discuss.elastic.co/t/mapping-conflict/40248/6 "2016-01-29T11:34:13Z")

</div>

Thanks, great work! I have a few questions about some points of the blog post:

- If I have multiple indexes (for example "logstash-YYYY.MM.DD"), can I do the same thing using as index "logstash- \*" or do I have to reschedule the logstash input for each index?

- If I don't have a new cluster, but I work on one as input and output, I will overwrite the old data or the data will be duplicated?

You talk about "first creating the mapping we want to apply before indexing any date", but considering the above (multiple indexes and clusters already existing), I can do the same this step?

---

_[View the full topic](https://discuss.elastic.co/t/mapping-conflict/40248)._