# Deprecation warnings since the upgrade to 7.4.0

**URL:** <https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917>\
**Category:** Elasticsearch\
**Created:** [October 2, 2019, 9:12am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917 "2019-10-02T09:12:31Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [October 20, 2019, 9:59am UTC](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917/8 "2019-10-20T09:59:36Z")

</div>

Thanks @stefws, I think that is consistent with the issue mentioned above, and a fix will be available in 7.4.1. This other thread has a temporary workaround for 7.4.0 if the warnings are intolerable, but otherwise I'd recommend leaving it alone and upgrading when the fix is released.

> [@Transport.publish\_address was printed as \[ip:port\] instead of \[hostname/ip:port\]](https://discuss.elastic.co/t/transport-publish-address-was-printed-as-ip-port-instead-of-hostname-ip-port/202519/6):
>
> I don't have the code in front of me right now, but if I remember correctly you can set es.http.cname\_in\_publish\_address to false to suppress this warning until 7.4.1 comes out.

---

_[View the full topic](https://discuss.elastic.co/t/deprecation-warnings-since-the-upgrade-to-7-4-0/201917)._