# Copy\_to or new index for ambiguous mapping

**URL:** <https://discuss.elastic.co/t/copy-to-or-new-index-for-ambiguous-mapping/59643>\
**Category:** Elasticsearch\
**Created:** [September 2, 2016, 8:38am UTC](https://discuss.elastic.co/t/copy-to-or-new-index-for-ambiguous-mapping/59643 "2016-09-02T08:38:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cristiana\_Tiugan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cristiana_tiugan/32/93274_2.png) [@Cristiana\_Tiugan](https://discuss.elastic.co/u/Cristiana_Tiugan)\
**Post date:** [September 2, 2016, 8:38am UTC](https://discuss.elastic.co/t/copy-to-or-new-index-for-ambiguous-mapping/59643/1 "2016-09-02T08:38:02Z")

</div>

Hello!  
I have a question regarding the changes about mapping in elasticsearch 2.3  
I have an index topic that has 2 types topic and tag. Each type has a property 'name' that unfortunately has a different meaning. In person represents the name of the topic and in tag the name of the tag.  
I am going to use a lot of aggregations on this index so I am not sure if the right solution is to create a separate index for tag or to use the copy\_to and copy the name of the tag into a new field.

---

<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:22pm UTC](https://discuss.elastic.co/t/copy-to-or-new-index-for-ambiguous-mapping/59643/2 "2017-07-05T22:22:58Z")

</div>

Closed on July 5, 2017, 10:22pm UTC