I was really excited to hear that custom _all fields are coming to town,
but the removal of per field boosting messed up my idea.
All I want to achieve is to create multiple _all-like fields consisting of
different fields (each _all-like field would gather data in different
language) and to query against them. I also badly need to boost some of the
fields (e.g. for books, title is far more important then the publisher). Each
of those fields would gather about 10 different fields. My current solution
is to store different languages in different indices but that solution
makes me duplicate a lot of language independant data. As stated in
https://github.com/elasticsearch/elasticsearch/pull/4972 I tried to use
multi_match or even string query with multiple fields but the performance
of that kind of query is nowhere close to querying the _all field itself.
Are per field boosting for custom _all fields planned to be reimplemented?
Will there be a significant improvement to how cross field multi_match
Could you think of another approach that could be worth trying?
I'd be grateful for any hints.
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/52067048-8eea-4e96-b285-c05f4a134dc6%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.