# ElasticSearch 7.0 upgrade from 6.7.1 issue with Metricbeat templates

**URL:** https://discuss.elastic.co/t/elasticsearch-7-0-upgrade-from-6-7-1-issue-with-metricbeat-templates/177418
**Category:** Elasticsearch
**Created:** [April 18, 2019, 9:05am UTC](https://discuss.elastic.co/t/elasticsearch-7-0-upgrade-from-6-7-1-issue-with-metricbeat-templates/177418 "2019-04-18T09:05:18Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![json](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/json/32/4125_2.png) [@json](https://discuss.elastic.co/u/json)
#### Post date: [April 26, 2019, 1:50pm UTC](https://discuss.elastic.co/t/elasticsearch-7-0-upgrade-from-6-7-1-issue-with-metricbeat-templates/177418/2 "2019-04-26T13:50:54Z")

</div>

Hi Roger,

Interesting. `metricbeat-7.0.0` should have the `index.query.default_field` setting in the template. Can you check `GET /_template/metricbeat-7.0.0`?

The setting was added to the Metricbeat template in libbeat 6.7.x per [https://github.com/elastic/beats/pull/11205](https://github.com/elastic/beats/pull/11205).

You can set `indices.query.bool.max_clause_count: 2000` in `elasticsearch.yml` to avoid any issues during the upgrade.

Jason

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-7-0-upgrade-from-6-7-1-issue-with-metricbeat-templates/177418)._