# Shingle Filter behaviour in Elasticsearch 1.0 **URL:** \ **Category:** Elasticsearch\ **Created:** [March 21, 2014, 12:49pm UTC](https://discuss.elastic.co/t/shingle-filter-behaviour-in-elasticsearch-1-0/16524 "2014-03-21T12:49:07Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jorjives](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jorjives/32/1706_2.png) [@jorjives](https://discuss.elastic.co/u/jorjives)\ **Post date:** [March 21, 2014, 12:49pm UTC](https://discuss.elastic.co/t/shingle-filter-behaviour-in-elasticsearch-1-0/16524/1 "2014-03-21T12:49:07Z")
Hello All, I'm trying to figure out a little problem in ES 1.0. When using 0.90 I have for a filter that pushes words together by shingling with an empty token separator, however, since upgrading to 1.0 it seems to switch to a space if the token\_separator field is empty (i.e. token\_filter: ""). I've managed to get around this by pattern replacing spaces with "" after it's shingled. I just wanted to check if this was the expected behaviour now? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/2f64a4ef-2bab-4bf1-ac09-ccebf3a6018c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2f64a4ef-2bab-4bf1-ac09-ccebf3a6018c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 1:41am UTC](https://discuss.elastic.co/t/shingle-filter-behaviour-in-elasticsearch-1-0/16524/2 "2017-07-06T01:41:36Z")