Set max from/size for ES about es-wp-query HOT 2 OPEN

For example, what happens when a bot tries to walk all archive pages.

That's a problem in MySQL too. I wonder which handles it better.

from es-wp-query.

BTW, there are ways to get around this sometimes with filters. May be worth implementing. For inf scroll of calypso posts, sorted by date across all of a user's blogs we use encoded page handles. Something like:

$args = wp_parse_args( “blog=1234&post=12&value=2015-01-12T12:00:21” )
{ “bool” : { “should” : [
  { “range” : { “date” : { “lt” : $args[‘date’] },
  { “and” : [
    { “term” : { “date” : $args[‘date’] },
    { “range” : { “blog_id” : { “gte” : $args[‘blog’] },
    { “range” : { “post_id” : { “gt” : $args[‘post’] },
  ] }
],
“sort” : [
  { “date” : { “order” : “desc” } },
  { “blog_id” : { “order” : “asc” } },
  { “post_id” : { “order” : “asc” } },
]
} }

Though the assumption here is that you need to pass around info about the last item that was shown rather than just a page number. It also has the nice property of not showing duplicate content when new content is posted. I suspect though that this would require a change to Core first. But mentioning in case there is another way.

from es-wp-query.