# The colon character is not being treated as a word separator/boundary
**URL:** https://discuss.elastic.co/t/the-colon-character-is-not-being-treated-as-a-word-separator-boundary/8436
**Category:** Elasticsearch
**Created:** [July 17, 2012, 2:11pm UTC](https://discuss.elastic.co/t/the-colon-character-is-not-being-treated-as-a-word-separator-boundary/8436 "2012-07-17T14:11:14Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@jack\_3](https://discuss.elastic.co/u/jack_3)
#### Post date: [July 17, 2012, 2:11pm UTC](https://discuss.elastic.co/t/the-colon-character-is-not-being-treated-as-a-word-separator-boundary/8436/1 "2012-07-17T14:11:14Z")
I reviewed elasticsearch documentation and still I am not sure how build
correctly curl xput query where I will set up colon character ":" like word
delimiter.
My database has many logstash indexers - logstash-%{+YYYY.MM.dd} with
@message field, where I need find string "failure", the problem is that I
can find result using "failure:request"
Can I resolve it global or I need add xput query to new logstash indexer?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 3:20am UTC](https://discuss.elastic.co/t/the-colon-character-is-not-being-treated-as-a-word-separator-boundary/8436/2 "2017-07-06T03:20:08Z")