# During writing data to Elasticsearch I get "object mapping for \[fields.args\] tried to parse field \[null\] as object, but found a concrete value"
**URL:** https://discuss.elastic.co/t/during-writing-data-to-elasticsearch-i-get-object-mapping-for-fields-args-tried-to-parse-field-null-as-object-but-found-a-concrete-value/221863
**Category:** Elasticsearch
**Created:** [March 3, 2020, 11:03am UTC](https://discuss.elastic.co/t/during-writing-data-to-elasticsearch-i-get-object-mapping-for-fields-args-tried-to-parse-field-null-as-object-but-found-a-concrete-value/221863 "2020-03-03T11:03:25Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@George\_Wainwright](https://discuss.elastic.co/u/George_Wainwright)
#### Post date: [March 3, 2020, 11:03am UTC](https://discuss.elastic.co/t/during-writing-data-to-elasticsearch-i-get-object-mapping-for-fields-args-tried-to-parse-field-null-as-object-but-found-a-concrete-value/221863/1 "2020-03-03T11:03:25Z")
I have the next Warning message when logstash tries to push data to Elasticsearch:
`object mapping for [fields.args] tried to parse field [null] as object, but found a concrete value`
I've noticed that in logs fields.args structure is being changed periodically.
In one case this is array:
fields.args: [9,"2020-03-03"]
In another case for example - this is mapping:
fields.args.id general\_theme
May it be the reason of these warnings?
I use latest version of filebeat elasticsearch logstash and Kibana which is 7.6.0
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 31, 2020, 11:03am UTC](https://discuss.elastic.co/t/during-writing-data-to-elasticsearch-i-get-object-mapping-for-fields-args-tried-to-parse-field-null-as-object-but-found-a-concrete-value/221863/2 "2020-03-31T11:03:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.