# Upgradation from 1.3.7 to 2.x **URL:** \ **Category:** Elasticsearch\ **Created:** [January 30, 2016, 5:22am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538 "2016-01-30T05:22:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![justnj](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@justnj](https://discuss.elastic.co/u/justnj)\ **Post date:** [January 30, 2016, 5:22am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/1 "2016-01-30T05:22:53Z")
Hi we are planning to upgrade ES from 1.3.7 to 2.X we have used migration plug and found lot conflict mappings with respect to various types. Each type has it own purpose to store records and retrival from an index. How can I have unique field name and data type, analyser for various TYPES. also how many maximum index I can create in a cluster If i have multiple types /can I store it in different indexes... Limitation of no of indexes and shards size with respect to cluster is there any easiest way to update a common mapping for fields for various types? ---
**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:** [January 30, 2016, 8:54am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/2 "2016-01-30T08:54:46Z")
> [@justnj](#): > > How can I have unique field name and data type, analyser for various TYPES. Have different types in different indices. > [@justnj](#): > > also how many maximum index I can create in a cluster Theoretically there are no limits, practically there are, but I can't tell you what that is as it depends on your cluster. > [@justnj](#): > > is there any easiest way to update a common mapping for fields for various types? No, you will need to reindex. ---
**Author:** ![justnj](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@justnj](https://discuss.elastic.co/u/justnj)\ **Post date:** [January 30, 2016, 10:11am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/3 "2016-01-30T10:11:19Z")
> [@warkolm](#): > > also how many maximum index I can create in a cluster can we use copy\_to to customize the fields to have unique mapping.will it cause any issues during indexing or searching... ...will it be deprecated in future version ---
**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:** [January 30, 2016, 7:47pm UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/4 "2016-01-30T19:47:19Z")
It's not being deprecated AFAIK. ---
**Author:** ![Selvam\_ayyanar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/selvam_ayyanar/32/11101_2.png) [@Selvam\_ayyanar](https://discuss.elastic.co/u/Selvam_ayyanar)\ **Post date:** [February 1, 2016, 7:19am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/5 "2016-02-01T07:19:51Z")
Hi @warkolm **any issue with using "copy\_to".** 1. we used "copy\_to" to solve mapping conflicts, in that we insert "index": no This may cause any issues while searching or indexing? ---
**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 1, 2016, 9:28pm UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/6 "2016-02-01T21:28:10Z")
If you don't index it you cannot search on it. ---
**Author:** ![Selvam\_ayyanar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/selvam_ayyanar/32/11101_2.png) [@Selvam\_ayyanar](https://discuss.elastic.co/u/Selvam_ayyanar)\ **Post date:** [February 2, 2016, 7:28am UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/7 "2016-02-02T07:28:37Z")
@warkolm Is it able to index a document when using "index": no. ex. "accountId" : { "type" : "string", "index" : "no", "copy\_to": "accountId\_308" }, "accountId\_308": { "type": "long" } in the above case, only able to index **accountId** in a **long** data format, my question is able to retrieve a data from accountId, for ex. accountId.value is it possible? ---
**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 3, 2016, 10:09pm UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/8 "2016-02-03T22:09:16Z")
You can retrieve it via a get with the document ID, but you cannot search on it. ---
**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:19pm UTC](https://discuss.elastic.co/t/upgradation-from-1-3-7-to-2-x/40538/9 "2017-07-05T23:19:11Z")