Has anyone implemented protection against deep paging inside Solr? I’m thinking about something like a max_rows parameter, where if start+rows was greater than that, it would limit the max result to that number. Or maybe just return a 400, that would be OK too.
I’ve had three or four outages caused by deep paging over the past dozen years with Solr. We implement a limit in the client code, then someone forgets to add it to the redesigned client code. A limit in the request handler would be so much easier. And yes, I know about cursor marks. We don’t want to enable deep paging, we want to stop it. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog)
