# KV field\_split prevents logstash ingesting data

**URL:** https://discuss.elastic.co/t/kv-field-split-prevents-logstash-ingesting-data/100434
**Category:** Logstash
**Created:** [September 14, 2017, 12:46am UTC](https://discuss.elastic.co/t/kv-field-split-prevents-logstash-ingesting-data/100434 "2017-09-14T00:46:35Z")
**Posts on this page:** 1
**Showing post:** 18

<div class="post-metadata">

### Author: ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)
#### Post date: [September 20, 2017, 7:00am UTC](https://discuss.elastic.co/t/kv-field-split-prevents-logstash-ingesting-data/100434/18 "2017-09-20T07:00:06Z")

</div>

The fields in the mapping only matches some of your fields. If you enable the kv parsing and alter the elasticsearch output to write to a new index, does any data get inserted then? If so, what does the mappings look like?

You could also try to write records to a file using a json\_lines codec. This would allow you to inspect the data and see if there are any fields that are generated and might cause a mapping conflict.

---

_[View the full topic](https://discuss.elastic.co/t/kv-field-split-prevents-logstash-ingesting-data/100434)._