# Elasticsearch 1.6.x to 2.3.x migration

**URL:** <https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533>\
**Category:** Elasticsearch\
**Created:** [May 9, 2016, 9:51am UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533 "2016-05-09T09:51:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cto](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@cto](https://discuss.elastic.co/u/cto)\
**Post date:** [May 9, 2016, 9:51am UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533/1 "2016-05-09T09:51:35Z")

</div>

Hi,

We have been using elasticsearch as a data-store for our application.

In the application, we were storing various devices and their outputs values.  
For storing all the device's details like name or other parameters, we have a "type" called **_master_**.  
And all the device output values are stored in "_type_" which is same as the device-name. This was done for faster searching.

When we used to delete a device, we used the delete the device from the master type and delete the "type" with the same device name.

But with the new version of elasticseach, we are not able to delete the type anymore. We can delete all the documents in the type.

So, will many unused type create a problem with huge data-set (700GB+)? Will it affect the performance?

Is there any work-around for this??

Thanks in advance

---

<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:** [May 9, 2016, 10:49am UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533/2 "2016-05-09T10:49:08Z")

</div>

The best option is to split things into their own indices.

You may want to reindex to 2.X anyway, to take advantage of doc values.

---

<div class="post-metadata">

**Author:** ![cto](https://avatars.discourse-cdn.com/v4/letter/c/5daacb/32.png) [@cto](https://discuss.elastic.co/u/cto)\
**Post date:** [May 10, 2016, 5:00am UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533/3 "2016-05-10T05:00:03Z")

</div>

In the application, a user is an index and all its devices types. some users have more than 10000 devices. Having so many indices won't effect the performance???

---

<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:** [May 10, 2016, 7:03am UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533/4 "2016-05-10T07:03:10Z")

</div>

Ah ok.

Well you have a choice to make, use the delete by query plugin, use multiple indices, or just leave the data and then delete it using your higher level retention policy.

---

<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, 10:52pm UTC](https://discuss.elastic.co/t/elasticsearch-1-6-x-to-2-3-x-migration/49533/5 "2017-07-05T22:52:53Z")

</div>