# Tokenize fix protocol non-printable delimiter

**URL:** <https://discuss.elastic.co/t/tokenize-fix-protocol-non-printable-delimiter/156569>\
**Category:** Elasticsearch\
**Created:** [November 14, 2018, 2:33am UTC](https://discuss.elastic.co/t/tokenize-fix-protocol-non-printable-delimiter/156569 "2018-11-14T02:33:34Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpresley](https://avatars.discourse-cdn.com/v4/letter/j/b38774/32.png) [@jpresley](https://discuss.elastic.co/u/jpresley)\
**Post date:** [November 14, 2018, 2:33am UTC](https://discuss.elastic.co/t/tokenize-fix-protocol-non-printable-delimiter/156569/1 "2018-11-14T02:33:35Z")

</div>

The fix protocol uses a non-printable character \001 as a delimiter with a key value pair separated by =. At this stage, we just need to search for the key value pair, e.g. "35=5". Is there a way to create a tokenizer that uses a non-printable character character? The pattern tokenizer looks like the right path if I knew how to pass a non-printable character to the pattern field.

---

<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, 2018, 2:33am UTC](https://discuss.elastic.co/t/tokenize-fix-protocol-non-printable-delimiter/156569/2 "2018-12-12T02:33:39Z")

</div>

Closed on December 12, 2018, 2:33am UTC

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