# S3 CSV Codec - Using a non printable character as separator

**URL:** <https://discuss.elastic.co/t/s3-csv-codec-using-a-non-printable-character-as-separator/282262>\
**Category:** Logstash\
**Created:** [August 23, 2021, 4:36pm UTC](https://discuss.elastic.co/t/s3-csv-codec-using-a-non-printable-character-as-separator/282262 "2021-08-23T16:36:16Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [August 24, 2021, 3:30am UTC](https://discuss.elastic.co/t/s3-csv-codec-using-a-non-printable-character-as-separator/282262/4 "2021-08-24T03:30:30Z")

</div>

An interesting related post is [here](https://discuss.elastic.co/t/logstash-http-poller-body-escape-double-and-single-quotation-marks/282039/2). In that case \u00xx works inside a string, but not because logstash decodes it. I would guess something in Manticore decodes it, or else on the receiving end in elasticsearch. It will not work here.

---

_[View the full topic](https://discuss.elastic.co/t/s3-csv-codec-using-a-non-printable-character-as-separator/282262)._