# Resolving deprecation warnings to allow us to upgrade

**URL:** https://discuss.elastic.co/t/resolving-deprecation-warnings-to-allow-us-to-upgrade/178038
**Category:** Elasticsearch
**Created:** [April 23, 2019, 12:07pm UTC](https://discuss.elastic.co/t/resolving-deprecation-warnings-to-allow-us-to-upgrade/178038 "2019-04-23T12:07:58Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![cowensel](https://avatars.discourse-cdn.com/v4/letter/c/eb9ed0/32.png) [@cowensel](https://discuss.elastic.co/u/cowensel)
#### Post date: [April 24, 2019, 11:26am UTC](https://discuss.elastic.co/t/resolving-deprecation-warnings-to-allow-us-to-upgrade/178038/5 "2019-04-24T11:26:40Z")

</div>

Hi David,

We do not specify a specific mapping we use the default logstash mapping. How do we remove the

`> [_default_] mapping` from being referenced in the output to elasticsearch same with the include\_type\_name

---

_[View the full topic](https://discuss.elastic.co/t/resolving-deprecation-warnings-to-allow-us-to-upgrade/178038)._