# CSV parse failure and some untraceable records

**URL:** <https://discuss.elastic.co/t/csv-parse-failure-and-some-untraceable-records/107499>\
**Category:** Logstash\
**Created:** [November 14, 2017, 7:25am UTC](https://discuss.elastic.co/t/csv-parse-failure-and-some-untraceable-records/107499 "2017-11-14T07:25:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aditi\_Shah](https://avatars.discourse-cdn.com/v4/letter/a/a3d4f5/32.png) [@Aditi\_Shah](https://discuss.elastic.co/u/Aditi_Shah)\
**Post date:** [November 14, 2017, 7:25am UTC](https://discuss.elastic.co/t/csv-parse-failure-and-some-untraceable-records/107499/1 "2017-11-14T07:25:43Z")

</div>

I have like 2 million records, out of which 40 did not get read, 11 of them are giving CSV parse failure and these rows are just like the other rows.  
Remaining 29, I cannot track which rows are they. There is no information about them in either es logs or logstash logs.  
I know es hasn't deleted them as my docs.deleted on localhost:9200/\_cat/index is 0.  
My logstash logs gave me csv parse failure for these 11 rows.

My CSV uses ## as separator.

Kindly help 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 12, 2017, 7:25am UTC](https://discuss.elastic.co/t/csv-parse-failure-and-some-untraceable-records/107499/2 "2017-12-12T07:25:44Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.