Answering myself:
According to ES blog
http://www.elasticsearch.org/blog/understanding-query-then-fetch-vs-dfs-query-then-fetch/
there is performance hit. It would be nice to have a feature that triggers
automatically DFS based on a kinda threshold...
On Wednesday, November 5, 2014 2:44:14 PM UTC+1, Sofiane Cherchalli wrote:
According to
Elasticsearch Platform — Find real-time answers at scale | Elastic,
the relevance is broken until we have enough data distributed uniformly
across shards.My question is: If I initially use the ?search_type=dfs_query_then_fetch
parameter because I few data, will it affect the performance when the
Production environment will have enough data sharded uniformly?Thanks.
--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/2d535fce-8df3-4e13-9259-b017a11ac634%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.