# Conflicting mappings

**URL:** <https://discuss.elastic.co/t/conflicting-mappings/42680>\
**Category:** Elasticsearch\
**Created:** [February 25, 2016, 8:14am UTC](https://discuss.elastic.co/t/conflicting-mappings/42680 "2016-02-25T08:14:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TDV](https://avatars.discourse-cdn.com/v4/letter/t/f475e1/32.png) [@TDV](https://discuss.elastic.co/u/TDV)\
**Post date:** [February 25, 2016, 8:14am UTC](https://discuss.elastic.co/t/conflicting-mappings/42680/1 "2016-02-25T08:14:03Z")

</div>

Hi  
We use Elastic 2.1.1 on Windows server 2012 R2

And we faced with mappings conflict problem described in "Conflicting doc values in mappings causes shard initialization failures" - [https://github.com/elastic/elasticsearch/issues/16563](https://github.com/elastic/elasticsearch/issues/16563)

There said that it will be fixed in 2.3.0 release - when will be 2.3.0 Elastic release?

---

<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:** [February 26, 2016, 12:12am UTC](https://discuss.elastic.co/t/conflicting-mappings/42680/2 "2016-02-26T00:12:39Z")

</div>

2.3 will probably be out next month.

---

<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:13pm UTC](https://discuss.elastic.co/t/conflicting-mappings/42680/3 "2017-07-05T23:13:29Z")

</div>

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