Re: Wildcard search on raw not_analyzed field

2015-03-31 Thread BradVido
Update, it seems that the problem is lowercase_expanded_terms defaults to true. Setting it to false in my query returned results for the first two queries. On Monday, January 26, 2015 at 5:04:44 PM UTC-6, BradVido wrote: > > I have a dynamic template that sets up not_analyzed raw mappings for al

Re: Wildcard search on raw not_analyzed field

2015-03-31 Thread BradVido
I need help determining how wildcard matching for non_analyzed fields works. I have a field `message` with this mapping defined: "message" : { "type" : "string", "norms" : { "enabled" : false }, "fields" : { "raw" : { "type" : "string", "index" : "not_analyzed", "doc_values" : true, "ignore_above"

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread BradVido
I am already doing a query text search. I'm expecting the ? to match a single character. It works on the regular, analyzed, field, just not the .raw not_analyzed version. That's why i'm confused -- You received this message because you are subscribed to the Google Groups "elasticsearch" group

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
First of all you have to use "regexp" filter or query, not "match". If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "alue". Like this: { "que

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
First of all you have to use "regexp" filter or query, not "match". If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "alue". Like this: { "que

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
First of all you have to use "regexp" filter or query, not "match". If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "alue". Like this: { "que

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
First of all you have to use "regexp" filter or query, not "match". If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "alue". Like this: { "que

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
First of all you have to use "regexp" filter or query, not "match". If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "value". Like this: { "qu

Re: Wildcard search on raw not_analyzed field

2015-01-28 Thread Roman Drogolov
If you mean any character between "Known" and "alue", you have to use dot instead of question mark. "Known?alue" means "Know" + ("n" or nothing) + "alue". "Known.alue" means "Known" + any character + "value". On Tuesday, January 27, 2015 at 1:04:44 AM UTC+2, BradVido wrote: > > I have a dynamic

Wildcard search on raw not_analyzed field

2015-01-26 Thread BradVido
I have a dynamic template that sets up not_analyzed raw mappings for all my string fields. When I perform a query search like this: field.raw=KnownValue it works (has hits). When I do this: field.raw=Known?alue it doesn't return any data (? wildcard doesn't work). However, field.raw=* does