# Field expansion matches too many fields, limit: 1024, got: 1369 with filebeat-6.6.0 indexes

**URL:** <https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720>\
**Category:** Elasticsearch\
**Created:** [April 26, 2019, 8:07pm UTC](https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720 "2019-04-26T20:07:09Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![opoplawski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/opoplawski/32/40442_2.png) [@opoplawski](https://discuss.elastic.co/u/opoplawski)\
**Post date:** [April 26, 2019, 8:07pm UTC](https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720/1 "2019-04-26T20:07:09Z")

</div>

We're running elasticsearch 7.0 but are still importing data from some filebeat-6.6.0 systems though logstash. Running queries in kibana we see shard failures and elastic reports:

```
Caused by: java.lang.IllegalArgumentException: field expansion matches too many fields, limit: 1024, got: 1369

```

I can fix this manually in kibana, but new indexes keep having this problem. Is there some way to prevent it before hand?

---

<div class="post-metadata">

**Author:** ![gbrown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gbrown/32/34482_2.png) [@gbrown](https://discuss.elastic.co/u/gbrown)\
**Post date:** [May 3, 2019, 4:42pm UTC](https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720/2 "2019-05-03T16:42:45Z")

</div>

You'll need to update the Filebeat index template to set the `index.query.default_field` setting as described [here](https://www.elastic.co/guide/en/beats/libbeat/7.0/troubleshooting-upgrade.html#dashboard-shard-failed) - you'll just update the index template instead of updating the index.

You can find information on how to retrieve and update index templates [here](https://www.elastic.co/guide/en/elasticsearch/reference/7.0/indices-templates.html).

---

<div class="post-metadata">

**Author:** ![opoplawski](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/opoplawski/32/40442_2.png) [@opoplawski](https://discuss.elastic.co/u/opoplawski)\
**Post date:** [May 6, 2019, 2:40pm UTC](https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720/3 "2019-05-06T14:40:02Z")

</div>

Thanks. I pulled the index.query.default\_field setting from the filebeat-7.0 template and added it to the filebeat-6.6.0 one and that appears to have done the trick.

---

<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:** [June 3, 2019, 2:40pm UTC](https://discuss.elastic.co/t/field-expansion-matches-too-many-fields-limit-1024-got-1369-with-filebeat-6-6-0-indexes/178720/4 "2019-06-03T14:40:07Z")

</div>

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