# Elastic Cloud - How to fix "number of fields exceeds the automatic field expansion limit"
**URL:** https://discuss.elastic.co/t/elastic-cloud-how-to-fix-number-of-fields-exceeds-the-automatic-field-expansion-limit/181921
**Category:** Elasticsearch
**Created:** [May 21, 2019, 5:20am UTC](https://discuss.elastic.co/t/elastic-cloud-how-to-fix-number-of-fields-exceeds-the-automatic-field-expansion-limit/181921 "2019-05-21T05:20:43Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Sjaak01](https://discuss.elastic.co/u/Sjaak01)
#### Post date: [May 21, 2019, 5:20am UTC](https://discuss.elastic.co/t/elastic-cloud-how-to-fix-number-of-fields-exceeds-the-automatic-field-expansion-limit/181921/1 "2019-05-21T05:20:44Z")
Hi,
On Elastic Cloud 6.7 and 6.8 I get the above warning when running the 7.0 upgrade assistant. How do I solve this?
I found you can set `indices.query.bool.max_clause_count` but Elastic Cloud does not allow modifying that value.
details:
> This index has [2409] fields, which exceeds the automatic field expansion limit of 1024 and does not have [index.query.default\_field] set, which may cause queries which use automatic field expansion, such as query\_string, simple\_query\_string, and multi\_match to fail if fields are not explicitly specified in the query.
---
### Author:  [@slmingol](https://discuss.elastic.co/u/slmingol)
#### Post date: [June 7, 2019, 2:27pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-to-fix-number-of-fields-exceeds-the-automatic-field-expansion-limit/181921/2 "2019-06-07T14:27:30Z")
> [@Sjaak01](#):
>
> indices.query.bool.max\_clause\_count
This page makes it sounds like you can change it if needed - [Search settings | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-settings.html).
> This setting limits the number of clauses a Lucene BooleanQuery can have. The default of 1024 is quite high and should normally be sufficient. This limit does not only affect Elasticsearchs `bool` query, but many other queries are rewritten to Lucene’s BooleanQuery internally. The limit is in place to prevent searches from becoming to large and taking up too much CPU and memory. In case you consider to increase this setting, make sure you exhausted all other options to avoid having to do this. Higher values can lead to performance degradations and memory issues, especially in clusters with a high load or few resources.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2019, 2:28pm UTC](https://discuss.elastic.co/t/elastic-cloud-how-to-fix-number-of-fields-exceeds-the-automatic-field-expansion-limit/181921/3 "2019-07-05T14:28:02Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.