# Multi\_match with no fields param try to match on not indexed fields, does it affect performance? **URL:** \ **Category:** Elasticsearch\ **Created:** [March 27, 2019, 3:21pm UTC](https://discuss.elastic.co/t/multi-match-with-no-fields-param-try-to-match-on-not-indexed-fields-does-it-affect-performance/174160 "2019-03-27T15:21:45Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![aspacca-gfg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aspacca-gfg/32/42904_2.png) [@aspacca-gfg](https://discuss.elastic.co/u/aspacca-gfg)\ **Post date:** [March 27, 2019, 3:21pm UTC](https://discuss.elastic.co/t/multi-match-with-no-fields-param-try-to-match-on-not-indexed-fields-does-it-affect-performance/174160/1 "2019-03-27T15:21:45Z")
Hello, I've a query with a multi\_match condition where I specify only the term and not the fields param `{"profile":true,"from":0,"query":{"multi_match":{"query":"test"}},"size":10}` In the profile output I can see a lot of the followings: `(MatchNoDocsQuery(\"failed [attributes.gender] query, caused by illegal_argument_exception:[Cannot search on field [attributes.gender] since it is not indexed.]\")` And indeed in my mapping for the index I set that fields with `index: false` and the results are the ones expected What I wonder about is if those exceptions affect query performances and I should rather "whitelist" all the indexed fields in the multi\_match query via the field param ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 24, 2019, 3:31pm UTC](https://discuss.elastic.co/t/multi-match-with-no-fields-param-try-to-match-on-not-indexed-fields-does-it-affect-performance/174160/2 "2019-04-24T15:31:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.