# Expected behavior for Upgrade Assistant 7.0 to show automatic field expansion warning even after changing max\_clause\_count?

**URL:** https://discuss.elastic.co/t/expected-behavior-for-upgrade-assistant-7-0-to-show-automatic-field-expansion-warning-even-after-changing-max-clause-count/188491
**Category:** Elasticsearch
**Created:** [July 2, 2019, 11:25am UTC](https://discuss.elastic.co/t/expected-behavior-for-upgrade-assistant-7-0-to-show-automatic-field-expansion-warning-even-after-changing-max-clause-count/188491 "2019-07-02T11:25:35Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![slmingol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/slmingol/32/12606_2.png) [@slmingol](https://discuss.elastic.co/u/slmingol)
#### Post date: [July 2, 2019, 11:25am UTC](https://discuss.elastic.co/t/expected-behavior-for-upgrade-assistant-7-0-to-show-automatic-field-expansion-warning-even-after-changing-max-clause-count/188491/1 "2019-07-02T11:25:36Z")

</div>

We're in the middle of upgrading from ES 6.8 to 7.1 and are trying to address guidances regarding 7.0 Upgrade Assistant. The Assistant is calling out the following issues on several indicies:

> This index has [1178] 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.

We've attempted to address this issue by changing this setting:

```auto
$ showcfg_cluster l | grep max_clau
    "indices.query.bool.max_clause_count" : "3072",

```

But the error/warning still remains. I found this [other question](https://discuss.elastic.co/t/elasticsearch-7-0-upgrade-from-6-7-1-issue-with-metricbeat-templates/177418/2) which leads one to believe that the continued display of the msg is normal and the issue has been resolved by overriding the max\_clause\_count but we'd like additional reassurances before proceeding.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/8/a/8ad61e6539964e54165f2ec2260064c15a65b044.png)

---

<div class="post-metadata">

### Author: ![slmingol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/slmingol/32/12606_2.png) [@slmingol](https://discuss.elastic.co/u/slmingol)
#### Post date: [July 4, 2019, 3:34am UTC](https://discuss.elastic.co/t/expected-behavior-for-upgrade-assistant-7-0-to-show-automatic-field-expansion-warning-even-after-changing-max-clause-count/188491/2 "2019-07-04T03:34:41Z")

</div>

I figured out that we can simply do the following to address the upgrade assistant warnings.

- Add `default_field: ["*"]` to each index's `_settings`.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/4/44ed547cb70630e575e649e01152aea19795b838.jpeg)

And override `"indices.query.bool.max_clause_count"` with a large enough number to handle our number of fields. For eg.

`"indices.query.bool.max_clause_count" : "3072",`

---

<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 1, 2019, 3:34am UTC](https://discuss.elastic.co/t/expected-behavior-for-upgrade-assistant-7-0-to-show-automatic-field-expansion-warning-even-after-changing-max-clause-count/188491/3 "2019-08-01T03:34:43Z")

</div>

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