Unless I am mistaken, that is already the job of the scan query, reducing the load caused by sorting a query. There would be no reduction by limiting the result set.
As I understand it the scan query identifies which shards has results, and then just starts serving the first results first without any sort. This continues until the shard has no more results. ElasticSearch only needs to track which results it has already sent, and sends the next batch, unsorted. This continues until you stop and the scan expires. On Fri, Apr 3, 2015 at 11:45 AM, Chen Wang <chen.apache.s...@gmail.com> wrote: > I was thinking that being able to do limit on ES side can reduce its query > load. > > -- > 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/-Y1wETKmuF0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/647b7cf9-1351-42d3-8238-fa2118b9f0b9%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CADqT7cH6w1EW%2B%2B%3Da%3D7C649dDReZOiCzB2X37hK%3DNiK%3D_Fs0FHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
