# Difficulty Keeping Pace With Breaking Changes

**URL:** <https://discuss.elastic.co/t/difficulty-keeping-pace-with-breaking-changes/135598>\
**Category:** Elasticsearch\
**Created:** [June 12, 2018, 8:52pm UTC](https://discuss.elastic.co/t/difficulty-keeping-pace-with-breaking-changes/135598 "2018-06-12T20:52:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bbrown](https://avatars.discourse-cdn.com/v4/letter/b/f07891/32.png) [@bbrown](https://discuss.elastic.co/u/bbrown)\
**Post date:** [June 12, 2018, 8:52pm UTC](https://discuss.elastic.co/t/difficulty-keeping-pace-with-breaking-changes/135598/1 "2018-06-12T20:52:14Z")

</div>

We are still using ES 1.7.5. We have an on-premises product used by let's just say more than a hundred, less than 10,000 customers.

We were hoping to move our customers to a more current version of ES, but unfortunately, have fields with dots in the name. We are now working on migrating our customers' indexes and moving to a more recent version, but I am dismayed by the wholesale removal of features such as types and parent-child queries that were fundamental to our initial adoption of the product.

We will probably initially target version 5.6 because, aside from the dots, it is reasonably compatible.

Do you foresee a time when Elasticsearch's programmatic interface and feature set become more stable?

---

<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 10, 2018, 8:52pm UTC](https://discuss.elastic.co/t/difficulty-keeping-pace-with-breaking-changes/135598/2 "2018-07-10T20:52:19Z")

</div>

Closed on July 10, 2018, 8:52pm UTC

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