# Wild card queries do not work after normalization
**URL:** https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386
**Category:** Elasticsearch
**Created:** [June 30, 2017, 8:13am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386 "2017-06-30T08:13:50Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@Nazar\_Dzepchuk](https://discuss.elastic.co/u/Nazar_Dzepchuk)
#### Post date: [June 30, 2017, 8:13am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/1 "2017-06-30T08:13:51Z")
**I have next model for elastic:**
{
"dev-dzep": {
"aliases": {},
"mappings": {
"usersearchmodel": {
"properties": {
"firstName": {
"type": "string",
"analyzer": "lowerKeyword"
}
}
}
},
"settings": {
"index": {
"creation\_date": "1498805992106",
"analysis": {
"analyzer": {
"standard": {
"filter": [
"standard",
"lowercase",
"stop"
],
"char\_filter": [
"icu\_normalizer"
],
"type": "custom",
"tokenizer": "standard"
},
"lowerKeyword": {
"filter": [
"lowercase",
"icu\_normalizer"
],
"char\_filter": [
"icu\_normalizer"
],
"type": "custom",
"tokenizer": "keyword"
}
}
},
"number\_of\_shards": "5",
"number\_of\_replicas": "1",
"uuid": "iglps8zkRa2Q11JHgyAXeg",
"version": {
"created": "2040199"
}
}
},
"warmers": {}
}
}
**Next query doesn't work in such case:**
POST /dev-dzep/\_search
{
"from": 0,
"size": 15,
"track\_scores": true,
"sort": [
{
"id": {
"order": "asc"
}
}
],
"query": {
"bool": {
"must": [
{
"bool": {
"should": [
{
"wildcard": {
"firstName": {
"value": "\*lizéé"
}
}
}
]
}
}
]
}
}
}
**But exact match query gives correct result:**
POST /dev-dzep/\_search
{
"query": {
"match" : {
"firstName" : "Elizéé"
}
}
}
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 30, 2017, 8:34am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/2 "2017-06-30T08:34:59Z")
That's the expected behavior as wildcard queries are not analyzed.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 30, 2017, 8:36am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/3 "2017-06-30T08:36:07Z")
BTW "\*xyz" is one of the worse query to run on an elasticsearch cluster. It's like a full scan...
---
### Author:  [@Nazar\_Dzepchuk](https://discuss.elastic.co/u/Nazar_Dzepchuk)
#### Post date: [June 30, 2017, 10:40am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/4 "2017-06-30T10:40:11Z")
Is there any way to fix this when I need to find word partially. Something that I can use instead of wild card query.
Currently I see only one option - normalize data before elastic build index and use the same normalization for wild card search query.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [June 30, 2017, 11:02am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/5 "2017-06-30T11:02:17Z")
You can try query string query: [Query String Query | Elasticsearch Reference [5.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/query-dsl-query-string-query.html#_wildcards)
But again, let me paste part of the doc: [Wildcard Query | Elasticsearch Reference [5.4] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/5.4/query-dsl-wildcard-query.html)
> Note that this query can be slow, as it needs to iterate over many terms. In order to prevent extremely slow wildcard queries, a wildcard term should not start with one of the wildcards \* or ?.
---
### Author:  [@Nazar\_Dzepchuk](https://discuss.elastic.co/u/Nazar_Dzepchuk)
#### Post date: [June 30, 2017, 11:35am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/6 "2017-06-30T11:35:00Z")
Thanks.
Query string query works.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 28, 2017, 11:35am UTC](https://discuss.elastic.co/t/wild-card-queries-do-not-work-after-normalization/91386/7 "2017-07-28T11:35:10Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.