# Wildcard doesn't work the same after elasticsearch upgrade

**URL:** https://discuss.elastic.co/t/wildcard-doesnt-work-the-same-after-elasticsearch-upgrade/36585
**Category:** Elasticsearch
**Created:** [December 7, 2015, 10:57pm UTC](https://discuss.elastic.co/t/wildcard-doesnt-work-the-same-after-elasticsearch-upgrade/36585 "2015-12-07T22:57:44Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![repairshopr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/repairshopr/32/6476_2.png) [@repairshopr](https://discuss.elastic.co/u/repairshopr)
#### Post date: [December 7, 2015, 10:57pm UTC](https://discuss.elastic.co/t/wildcard-doesnt-work-the-same-after-elasticsearch-upgrade/36585/1 "2015-12-07T22:57:44Z")

</div>

Hey there, when we tested our ES upgrade from 1.7 to 2.1 it seems our wildcard search behavior changed.

Eg, we used to automatically get wildcards like:

name: "John"

We could query: "joh" and it would work

After the upgrade, we have to do "john" or "jo\*"

Is this an ES version thing, or something else we somehow broke???

(Another dev set this up)  
a snippet

```ruby
indexes :firstname, boost: 7, type: :string, index_analyzer: :autocomplete_analyzer, search_analyzer: :standard

```

snippet

```auto
      analyzer: {
        autocomplete_analyzer: {
          type: :custom,
          tokenizer: :standard,
          filter: ["standard", "lowercase", "autocomplete_filter"]
        },

```

Any ideas??

---

<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 5, 2017, 11:32pm UTC](https://discuss.elastic.co/t/wildcard-doesnt-work-the-same-after-elasticsearch-upgrade/36585/2 "2017-07-05T23:32:54Z")

</div>