# Resolving deprecation warnings using Default Logstash config to allow us to upgrade
**URL:** https://discuss.elastic.co/t/resolving-deprecation-warnings-using-default-logstash-config-to-allow-us-to-upgrade/178245
**Category:** Logstash
**Created:** [April 24, 2019, 12:18pm UTC](https://discuss.elastic.co/t/resolving-deprecation-warnings-using-default-logstash-config-to-allow-us-to-upgrade/178245 "2019-04-24T12:18:56Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@cowensel](https://discuss.elastic.co/u/cowensel)
#### Post date: [April 24, 2019, 12:18pm UTC](https://discuss.elastic.co/t/resolving-deprecation-warnings-using-default-logstash-config-to-allow-us-to-upgrade/178245/1 "2019-04-24T12:18:56Z")
I am currently going through the Elasticsearch deprecation logs to check what we may need to resolve prior to upgrading our ELK Stack from v6.0.0 where I have found the following but have no clue how to resolve. We have Logstash created Daily indices using the default settings is there a way in logstash to resolve the below errors?
`[o.e.d.a.a.i.t.p.PutIndexTemplateRequest] Deprecated field [template] used, replaced by [index_patterns]`
`Deprecated field [inline] used, expected [source] instead`
`[_default_] mapping is deprecated since it is not useful anymore now that indexes cannot have more than one type`
`Fielddata access on the _uid field is deprecated, use _id instead`
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 22, 2019, 12:32pm UTC](https://discuss.elastic.co/t/resolving-deprecation-warnings-using-default-logstash-config-to-allow-us-to-upgrade/178245/2 "2019-05-22T12:32:41Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.