# Flattened fields and \`query\_string\` queries with leading wildcard

**URL:** <https://discuss.elastic.co/t/flattened-fields-and-query-string-queries-with-leading-wildcard/373576>\
**Category:** Elasticsearch\
**Created:** [January 23, 2025, 11:52am UTC](https://discuss.elastic.co/t/flattened-fields-and-query-string-queries-with-leading-wildcard/373576 "2025-01-23T11:52:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ddittmar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ddittmar/32/140892_2.png) [@ddittmar](https://discuss.elastic.co/u/ddittmar)\
**Post date:** [January 23, 2025, 1:31pm UTC](https://discuss.elastic.co/t/flattened-fields-and-query-string-queries-with-leading-wildcard/373576/3 "2025-01-23T13:31:06Z")

</div>

Thanks for the reply... did you find any other solution?  
I've switched to `flattened` fields because I ran into the "Limit of total fields [1000] has been exceeded while adding new fields" Problem and found this thread: [Approaches to deal with “Limit of total fields [1000] in index has been exceeded”](https://discuss.elastic.co/t/approaches-to-deal-with-limit-of-total-fields-1000-in-index-has-been-exceeded/241039)

---

_[View the full topic](https://discuss.elastic.co/t/flattened-fields-and-query-string-queries-with-leading-wildcard/373576)._
