[Photon] Next steps

[Yohan Boniface]

"Also, accepts analyzer, boost, operator, minimum_should_match, 
zero_terms_query and cutoff_frequency, as explained in match query."

 From 
http://www.elasticsearch.org/guide/en/elasticsearch/reference/1.x/query-dsl-multi-match-query.html#type-cross-fields

So no "fuzzy", and we also asked on IRC IIRC.

But then cross_fields is not the silver bullet, because you weigth *per 
field* (which is nice), but you also want to weight differently if the 
query was fuzzy or not, which you can't do with a multimatch, even if we 
imagine that they add the fuzzyness also for cross fields, because it's 
set *per query*.

If you want to work on search logic, you should work on the positive 
scoring branch.


On 06/17/2014 06:23 PM, Peter K wrote:
> There is no official answer so I'm not sure if this is correct. E.g. in
> the code it does not look like there is a limit
>
> https://github.com/elasticsearch/elasticsearch/blob/9ed34b5a9e9769b1264bf04d9b9a674794515bc6/src/main/java/org/elasticsearch/index/query/MultiMatchQueryBuilder.java
>
> Also in this issue the talk about fuzziness (and link to another issue
> which is now closed):
> https://github.com/elasticsearch/elasticsearch/pull/5005
>
> Peter.
>
>> On 06/17/2014 06:05 PM, Christoph Lingg wrote:
>>> downside is apparently that fuzzy is not working, haven’t tried it
>>> yet. Are you sure about this yohan?
>>
>> Yes, that's why we eliminated this option quickly :/
>> See for example
>> https://groups.google.com/forum/#!topic/elasticsearch/mmdnRDsvvVA
>>
>>
>
>