# Re: Nested indices?

**URL:** <https://discuss.elastic.co/t/re-nested-indices/5261>\
**Category:** Elasticsearch\
**Created:** [August 26, 2011, 7:48pm UTC](https://discuss.elastic.co/t/re-nested-indices/5261 "2011-08-26T19:48:01Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karussell1](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@Karussell1](https://discuss.elastic.co/u/Karussell1)\
**Post date:** [August 26, 2011, 7:48pm UTC](https://discuss.elastic.co/t/re-nested-indices/5261/1 "2011-08-26T19:48:01Z")

</div>

why not use 'type' for computer or phone?

And if the indices are really big you can also split them by app but  
app can also be a simple property as well

On 15 Aug., 20:03, ajsie [johnny.weng....@gmail.com](mailto:johnny.weng....@gmail.com) wrote:

> I was thinking about nested indices.
> 
> Eg.
> 
> /:index1/:index2:/../:index3/:type:/:id
> 
> I have products that could be computers, phones etc.
> 
> Here are my options today:
> 
> /:app/computer/:id  
> /:app/phone/:id
> 
> or
> 
> /products/computer/:id  
> /products/phone/:id
> 
> or
> 
> /:app\_products/computer/:id  
> /:app\_products/phone/:id
> 
> If nested indices are allowed it could be:
> 
> /app1/products/computer/:id  
> /app1/products/phone/:id  
> /app2/products/computer/:id  
> /app2/products/phone/:id
> 
> Thoughts?

---

<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 6, 2017, 3:55am UTC](https://discuss.elastic.co/t/re-nested-indices/5261/2 "2017-07-06T03:55:52Z")

</div>

Closed on July 6, 2017, 3:55am UTC