# Changes to default tokenizer / analyzer in 2.x?

**URL:** <https://discuss.elastic.co/t/changes-to-default-tokenizer-analyzer-in-2-x/88776>\
**Category:** Elasticsearch\
**Created:** [June 9, 2017, 1:15am UTC](https://discuss.elastic.co/t/changes-to-default-tokenizer-analyzer-in-2-x/88776 "2017-06-09T01:15:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![a43](https://avatars.discourse-cdn.com/v4/letter/a/e19b73/32.png) [@a43](https://discuss.elastic.co/u/a43)\
**Post date:** [June 9, 2017, 1:15am UTC](https://discuss.elastic.co/t/changes-to-default-tokenizer-analyzer-in-2-x/88776/1 "2017-06-09T01:15:51Z")

</div>

We're upgrading from 1.x to 2.x and confused about possible changes in default behavior around the analyzer / tokenizer.

We index an object with a string field whose value contains a "." in it, for example, "123.abc".

In 1.x, we were able to treat that "." as a normal character, for example, searching for items whose field is an exact match on "123.abc" would work as expected. In 2.x, the same query returns no results. However, searching for "123" will return the item. How do we restore the behavior to what was happening in 1.x? Thanks!

---

<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:** [July 7, 2017, 1:16am UTC](https://discuss.elastic.co/t/changes-to-default-tokenizer-analyzer-in-2-x/88776/2 "2017-07-07T01:16:53Z")

</div>

Closed on July 7, 2017, 1:16am UTC

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