# Indexing a large number of fields

**URL:** <https://discuss.elastic.co/t/indexing-a-large-number-of-fields/193304>\
**Category:** Elasticsearch\
**Created:** [August 1, 2019, 10:46am UTC](https://discuss.elastic.co/t/indexing-a-large-number-of-fields/193304 "2019-08-01T10:46:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vaibhav97garg](https://avatars.discourse-cdn.com/v4/letter/v/b77776/32.png) [@vaibhav97garg](https://discuss.elastic.co/u/vaibhav97garg)\
**Post date:** [August 1, 2019, 10:46am UTC](https://discuss.elastic.co/t/indexing-a-large-number-of-fields/193304/1 "2019-08-01T10:46:08Z")

</div>

I am trying to bulk index a cluster with a large number of fields and everytime i send a request, it results in a timeout.  
I read somewhere this could happen because of mapping explosion.  
I am using the JAVA API and would like to know how can one disable indexing of some particular fields in the cluster while the others are indexed normally.

thank you!

---

<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:** [August 29, 2019, 10:46am UTC](https://discuss.elastic.co/t/indexing-a-large-number-of-fields/193304/2 "2019-08-29T10:46:20Z")

</div>

Closed on August 29, 2019, 10:46am UTC

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