# Why is catch-all field slower in 6.2 compared to 2.4?

**URL:** <https://discuss.elastic.co/t/why-is-catch-all-field-slower-in-6-2-compared-to-2-4/124374>\
**Category:** Elasticsearch\
**Created:** [March 16, 2018, 11:43pm UTC](https://discuss.elastic.co/t/why-is-catch-all-field-slower-in-6-2-compared-to-2-4/124374 "2018-03-16T23:43:29Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![diranged](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/diranged/32/4065_2.png) [@diranged](https://discuss.elastic.co/u/diranged)\
**Post date:** [April 11, 2018, 10:14pm UTC](https://discuss.elastic.co/t/why-is-catch-all-field-slower-in-6-2-compared-to-2-4/124374/4 "2018-04-11T22:14:13Z")

</div>

So I actually figured it out on our end. When you don't specify a field name, in ES 6 and Kibana 6, a default search parameter `default_field: "*"` is added by Kibana. Even if Kibana did not add that, ElasticSearch would add `default_field: "*.*"`. (\*\*)

To resolve this, we added a `copy_to: "all" mapping to all of our fields, and then reconfigured Kibana to use`all`as the`default\_field`. This resolves the speed issues entirely.

Unfortunately, we don;'t have the mapping quite right yet.. so we are still having issues. I opened up another post about it here: [Proper Template Mapping for ES/Kibana 6.2.3](https://discuss.elastic.co/t/proper-template-mapping-for-es-kibana-6-2-3/127700)

\*\*: [https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-query-string-query.html)

---

_[View the full topic](https://discuss.elastic.co/t/why-is-catch-all-field-slower-in-6-2-compared-to-2-4/124374)._