I have the same issue, I would like to be able to do a fuzzy search for
some of my fields in a multi_match query of type cross_fields. Right now I
have to do two queries but gives me a disjunct set rather than a
conjunctive result:
{
"query": {
"bool": {
"should": [
{
"multi_match": {
"query": "foo 500",
"type": "cross_fields",
"operator": "and",
"analyzer": "standard",
"fields": [
"display_name",
"strength_text",
"vnr",
"manufacturer",
"categories",
"amount_text",
"color_code",
"item_size_text"
]
}
},
{
"match": {
"display_name": {
"query": "foo 500",
"fuzziness": "auto"
}
}
}
]
}
},
"size": 150,
"from": 0
}
The second match query adds a bunch of hits which makes the first hit
irrelevant..
Does anyone have a solution to this?
Den torsdagen den 10:e april 2014 kl. 14:23:29 UTC+2 skrev Elliott Bradshaw:
>
> Any thoughts on this?
>
> The search type is really fantastic and we're already using it in
> production, but a fuzziness capability would add so much.
>
> On Monday, April 7, 2014 9:59:54 AM UTC-4, Elliott Bradshaw wrote:
>>
>> Hi Elasticsearch,
>>
>> I've been playing with the new cross_fields multi match type, and I've
>> got to say that I love it. It's a great way to search complex data without
>> doing a lot of memory killing denormalization. That said, is there any
>> plan to implement a fuzziness option with this type? That would certainly
>> be very valuable.
>>
>> - Elliott
>>
>
--
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 elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/90838e39-49c6-4446-abc8-1d2781ffd0e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
