# Interpretation of wildcards for field names in query

**URL:** <https://discuss.elastic.co/t/interpretation-of-wildcards-for-field-names-in-query/146236>\
**Category:** Elasticsearch\
**Created:** [August 27, 2018, 7:43pm UTC](https://discuss.elastic.co/t/interpretation-of-wildcards-for-field-names-in-query/146236 "2018-08-27T19:43:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![blevine](https://avatars.discourse-cdn.com/v4/letter/b/f475e1/32.png) [@blevine](https://discuss.elastic.co/u/blevine)\
**Post date:** [August 27, 2018, 7:43pm UTC](https://discuss.elastic.co/t/interpretation-of-wildcards-for-field-names-in-query/146236/1 "2018-08-27T19:43:54Z")

</div>

Hi all,

When issuing a query with a field like`*.content`, it appears that `'*'` matches all levels in the field name. In other words, this matches foo.content, foo.bar.content, foo.bar.baz.content, etc. For my particular use-case, I really only want to match foo.bar and not some 'bar' field that may be nested more deeply.

Is this possible?

---

<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:** [September 24, 2018, 7:43pm UTC](https://discuss.elastic.co/t/interpretation-of-wildcards-for-field-names-in-query/146236/2 "2018-09-24T19:43:58Z")

</div>

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