# Do EQL deprecations also imply deprecation of the Java API?

**URL:** <https://discuss.elastic.co/t/do-eql-deprecations-also-imply-deprecation-of-the-java-api/320462>\
**Category:** Elasticsearch\
**Created:** [December 5, 2022, 10:48am UTC](https://discuss.elastic.co/t/do-eql-deprecations-also-imply-deprecation-of-the-java-api/320462 "2022-12-05T10:48:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![martinwun](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/martinwun/32/114224_2.png) [@martinwun](https://discuss.elastic.co/u/martinwun)\
**Post date:** [December 5, 2022, 10:48am UTC](https://discuss.elastic.co/t/do-eql-deprecations-also-imply-deprecation-of-the-java-api/320462/1 "2022-12-05T10:48:50Z")

</div>

Hello,

in the release notes for 7.13 it states the following in the section on "EQL deprecations":  
"The `wildcard` function is deprecated."

> **[Migrating to 7.13 | Elasticsearch Guide \[7.17\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/migrating-7.13.html#breaking_713_eql_deprecations)**

What is not clear to me is whether or not this is also affecting the Java API. Does this deprecation mean that `QueryBuilders.wildcardQuery()` is also deprecated? (it doesn't say so in the 7.17.7 Java code, i.e. not `@Deprecated` annotation on this method).  
Thanks!

Cheers,  
Martin

---

<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:** [January 2, 2023, 10:49am UTC](https://discuss.elastic.co/t/do-eql-deprecations-also-imply-deprecation-of-the-java-api/320462/2 "2023-01-02T10:49:04Z")

</div>

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