# termFilter/termQuery and wildcard fieldnames **URL:** \ **Category:** Elasticsearch\ **Created:** [February 28, 2013, 5:56pm UTC](https://discuss.elastic.co/t/termfilter-termquery-and-wildcard-fieldnames/10955 "2013-02-28T17:56:45Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Bruce\_Ritchie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_ritchie/32/9370_2.png) [@Bruce\_Ritchie](https://discuss.elastic.co/u/Bruce_Ritchie)\ **Post date:** [February 28, 2013, 5:56pm UTC](https://discuss.elastic.co/t/termfilter-termquery-and-wildcard-fieldnames/10955/1 "2013-02-28T17:56:45Z")
Using 0.20.2, I've been attempting to get field name wildcards to work with term filter/query without any success as it only seems to work for normal field queries. For example, - this gist ([https://gist.github.com/Omega359/4b00e28bdb6533a8468a](https://gist.github.com/Omega359/4b00e28bdb6533a8468a)) shows a working query using a query filter - this gist ([https://gist.github.com/Omega359/a2bcb743950bcd84dd9a](https://gist.github.com/Omega359/a2bcb743950bcd84dd9a)) shows a working query using a term filter with a full path - this gist ([https://gist.github.com/Omega359/be0ce1838bb93e693c60](https://gist.github.com/Omega359/be0ce1838bb93e693c60)) which is the same as the second query with the only change being the wildcard in the fieldname Is this something that just won't work ever for a technical reason or rather is it something that just isn't implemented ? All the best, Bruce -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [March 1, 2013, 10:25am UTC](https://discuss.elastic.co/t/termfilter-termquery-and-wildcard-fieldnames/10955/2 "2013-03-01T10:25:55Z")
On Thursday, February 28, 2013 6:56:45 PM UTC+1, Bruce Ritchie wrote: > Using 0.20.2, I've been attempting to get field name wildcards to work > with term filter/query without any success as it only seems to work for > normal field queries. > > For example, > > - this gist ([gist:4b00e28bdb6533a8468a · GitHub](https://gist.github.com/Omega359/4b00e28bdb6533a8468a)) > shows a working query using a query filter > - this gist ([gist:a2bcb743950bcd84dd9a · GitHub](https://gist.github.com/Omega359/a2bcb743950bcd84dd9a)) > shows a working query using a term filter with a full path > - this gist ([gist:be0ce1838bb93e693c60 · GitHub](https://gist.github.com/Omega359/be0ce1838bb93e693c60)) > which is the same as the second query with the only change being the > wildcard in the fieldname > > Is this something that just won't work ever for a technical reason or > rather is it something that just isn't implemented ? in theory this could be implemented but it hasn't yet. simon > All the best, > > Bruce -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:48am UTC](https://discuss.elastic.co/t/termfilter-termquery-and-wildcard-fieldnames/10955/3 "2017-07-06T02:48:53Z")