# Question about index aliasing

**URL:** <https://discuss.elastic.co/t/question-about-index-aliasing/104623>\
**Category:** Elasticsearch\
**Created:** [October 19, 2017, 9:23pm UTC](https://discuss.elastic.co/t/question-about-index-aliasing/104623 "2017-10-19T21:23:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\
**Post date:** [October 19, 2017, 9:23pm UTC](https://discuss.elastic.co/t/question-about-index-aliasing/104623/1 "2017-10-19T21:23:38Z")

</div>

I am wondering if the following use case will work with indiex aliasing?

I have two indices **index1** and **index2** , both of them aliased to index **combinedindex**. Both these indices have different fields.

Basically, I have an index with too many fields and I just want to partition it. For example, if the actual index has 10,000 fields, I want fields 1-5000 to map to index1 and 5001-10,000 map to index2.

```
POST /_aliases
{
    "actions" : [
        { "add" : { "indices" : ["index1", "index2"], "alias" : "combinedindex" } }
    ]
}
```

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [October 23, 2017, 8:41am UTC](https://discuss.elastic.co/t/question-about-index-aliasing/104623/2 "2017-10-23T08:41:13Z")

</div>

This is not possible. You should also work on changing the number of fields in your indices, as fast as possible. This will hunt you forever, especially the more data and fields you add...

---

<div class="post-metadata">

**Author:** ![animageofmine](https://avatars.discourse-cdn.com/v4/letter/a/7feea3/32.png) [@animageofmine](https://discuss.elastic.co/u/animageofmine)\
**Post date:** [October 25, 2017, 11:15am UTC](https://discuss.elastic.co/t/question-about-index-aliasing/104623/3 "2017-10-25T11:15:58Z")

</div>

@spinscale Thank you. A few follow up questions that would help me understand your answer a bit more:

1. What is considered high as far as number of fields in an index is concerned? Does it depend on the type of fields?
2. Can you elaborate why would it hunt if I add more data and fields?
3. Is there any benchmarking done for ES customers as far as number of fields in an index is concerned?

---

<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:** [November 22, 2017, 11:16am UTC](https://discuss.elastic.co/t/question-about-index-aliasing/104623/4 "2017-11-22T11:16:04Z")

</div>

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