You could use edge ngrams:

http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-edgengram-tokenizer.html

Or if you have the correct version of ElasticSearch, you can use the 
Completion Suggester:

http://www.elasticsearch.org/blog/you-complete-me/

Dan



On Wednesday, April 9, 2014 8:53:21 AM UTC+1, cyrilforce wrote:
>
> Hi Dan,
>
> Good to know that. So what do you suggest if i wanted to have behavior 
> like when i type (search perform in multiple fields eg : DISPLAY_NAME and 
> PERFORMER)
>
> *Hel*
>
> Then it returns (in the following order) : 
> *Hel*l
> *Hel*p
> *Hel*lo
> *Hel*lo World
>
>
>
> On Wed, Apr 9, 2014 at 3:45 PM, Dan Tuffery <[email protected]<javascript:>
> > wrote:
>
>> The boost you define in the 'multi_match' query is not being show in the 
>> explain results, so it is not being applied to the score. It should be 
>> displayed in the weight, i.e.
>>
>> "description": "weight(DISPLAY_NAME^8:happy in 33593) 
>> [PerFieldSimilarity], result of:"
>>
>> The 'phrase_prefix' type is the issue, if you remove that type the boost 
>> will be applied. So it doesn't look like you can combine 'multi_match' 
>> boosting with the 'phrase_prefix' as the type.
>>
>> Dan
>>
>>
>> On Tuesday, April 8, 2014 5:15:38 PM UTC+1, cyrilforce wrote:
>>
>>> Hi Dan,
>>>
>>> I have enabled an analyzer in mapping due to stopword :
>>>
>>>  "*DISPLAY_NAME*": {
>>>                 "type": "string",
>>>                 "*analyzer*": "*standard*"
>>>    }
>>>
>>>
>>>
>>> *The query : *
>>>
>>>  "multi_match" : {
>>>           "query" : "*happy*",
>>>           "fields" : [ *"DISPLAY_NAME^8*", "*PERFORMER*" ],         
>>>           "type":   "*phrase_prefix*",
>>>           "operator" : "AND"
>>>         }
>>>
>>>
>>> *The result returned with explain enabled :*
>>> *https://gist.github.com/cheehoo/10149517 
>>> <https://gist.github.com/cheehoo/10149517>*
>>>
>>>  
>>>  Thanks          
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Apr 8, 2014 at 8:44 PM, Dan <[email protected]> wrote:
>>>
>>>>  Turn on the explain feature to see why  example 4 is not getting a 
>>>> higher score.
>>>>
>>>> http://www.elasticsearch.org/guide/en/elasticsearch/
>>>> reference/current/search-explain.html
>>>>
>>>> I suspect it has something to do with the way you are indexing your 
>>>> data. If you still have issues a gist would help us.
>>>>
>>>> Dan
>>>>
>>>>
>>>> On Tuesday, April 8, 2014 1:11:46 PM UTC+1, cyrilforce wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I have a query as below : 
>>>>>
>>>>>  "multi_match" : {
>>>>>           "query" : "*happy*",
>>>>>           "fields" : [ *"DISPLAY_NAME^8*", "*PERFORMER*" ],         
>>>>>           "type":   "*phrase_prefix*",
>>>>>           "operator" : "AND"
>>>>>         }
>>>>>
>>>>>
>>>>> Result return in the following order: 
>>>>> 1)
>>>>>  "_score": 2.1704028,
>>>>>                 "_source": {
>>>>>                     "DISPLAY_NAME": "*Happy*man",
>>>>>
>>>>> 2)
>>>>>  "_score": 1.4312989,
>>>>>                 "_source": {
>>>>>                     "DISPLAY_NAME": "Boishakh (Version 1)",
>>>>>                    "PERFORMER": "*Happy*",
>>>>>
>>>>> 3)
>>>>>  "_score": 1.2510761,
>>>>>                 "_source": {
>>>>>                     "DISPLAY_NAME": "Franzl Im Happysound",
>>>>>                    "PERFORMER": "Franzl & Die Psayrer",
>>>>>
>>>>> 4)
>>>>>      "_score": 1.0920545,
>>>>>                 "_source": {
>>>>>                     "DISPLAY_NAME": "*Happy*",
>>>>>                "PERFORMER": "Diandra Arjunaidi"
>>>>>
>>>>>
>>>>> As the result shown why the #4 have lesser score computed as i already 
>>>>> added a boost in the "DISPLAY_NAME^6" field. Is that the boost not 
>>>>> working 
>>>>> for multimatch phrase query ? 
>>>>>  
>>>>>
>>>>>
>>>>>  -- 
>>>> You received this message because you are subscribed to a topic in the 
>>>> Google Groups "elasticsearch" group.
>>>> To unsubscribe from this topic, visit https://groups.google.com/d/
>>>> topic/elasticsearch/yEAJ0Ym8PrU/unsubscribe.
>>>>  To unsubscribe from this group and all its topics, send an email to 
>>>> [email protected].
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/elasticsearch/bfd38ce9-13b0-4d25-912f-28036992a6df%
>>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/bfd38ce9-13b0-4d25-912f-28036992a6df%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> -- 
>>> Regards,
>>>
>>> Chee Hoo 
>>>
>>  -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "elasticsearch" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/elasticsearch/yEAJ0Ym8PrU/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/elasticsearch/96218594-90b7-43f4-a0f5-497da059c2f9%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/96218594-90b7-43f4-a0f5-497da059c2f9%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Regards,
>
> Chee Hoo 
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/608341a2-0d83-48cc-9126-40499553c58b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to