# Secondary indecies on field values

**URL:** <https://discuss.elastic.co/t/secondary-indecies-on-field-values/12457>\
**Category:** Elasticsearch\
**Created:** [June 18, 2013, 9:22am UTC](https://discuss.elastic.co/t/secondary-indecies-on-field-values/12457 "2013-06-18T09:22:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Perditor](https://avatars.discourse-cdn.com/v4/letter/p/65b543/32.png) [@Perditor](https://discuss.elastic.co/u/Perditor)\
**Post date:** [June 18, 2013, 9:22am UTC](https://discuss.elastic.co/t/secondary-indecies-on-field-values/12457/1 "2013-06-18T09:22:37Z")

</div>

I'm considering to use ElasticSearch as a search engine for large objects. There are about 500 millions objects on a single machine. For far is Elasticsearch a good solution for executing advanced queries. But a have the problem that i did find any technique to create secondary index on the document fields. Is in elasticsearch a possibility to create a secondary indecies like in MySQL on columns? Or are there any other technologies implemented to accelerate searches on field values? I'm using an single server enviroment and I have to store about 300 fields per row/object. At the moment there are about 500 million object in my database.

Thanks in advanced

---

<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, 2:30am UTC](https://discuss.elastic.co/t/secondary-indecies-on-field-values/12457/2 "2017-07-06T02:30:37Z")

</div>

Closed on July 6, 2017, 2:30am UTC