News for hackers. Stuff that matters.
Re:GitHub has 11,995,200 open issues by ekns on Wednesday April 27, 2016 @03:45AM (#11578515)
Funny how it says there's 479830 pages worth of results and even has a link to that "last page".

I checked and in practice it "only" returns the first 400 pages of results.

Re:GitHub has 11,995,200 open issues by g_sch on Wednesday April 27, 2016 @07:18AM (#11579367)
Isn't this because deep pagination is really costly? I've seen other production systems (especially using elasticsearch) where this limit is in place.

From Elastic:

>Deep Paging in Distributed Systems

>To understand why deep paging is problematic, let’s imagine that we are searching within a single index with five primary shards. When we request the first page of results (results 1 to 10), each shard produces its own top 10 results and returns them to the coordinating node, which then sorts all 50 results in order to select the overall top 10.

>Now imagine that we ask for page 1,000—results 10,001 to 10,010. Everything works in the same way except that each shard has to produce its top 10,010 results. The coordinating node then sorts through all 50,050 results and discards 50,040 of them!

>You can see that, in a distributed system, the cost of sorting results grows exponentially the deeper we page. There is a good reason that web search engines don’t return more than 1,000 results for any query.

https://www.elastic.co/guide/en/elasticsearch/guide/current/...

Re:GitHub has 11,995,200 open issues by stephengillie on Wednesday April 27, 2016 @04:41AM (#11578703)
That sounds like an issue. I wonder if someone's reported it...
Re:GitHub has 11,995,200 open issues by smonte on Wednesday April 27, 2016 @06:54AM (#11579287)
One more error to be reported in Danny Tuppeny's post from today http://blog.dantup.com/2016/04/have-software-developers-give...
Re:GitHub has 11,995,200 open issues by ashmud on Wednesday April 27, 2016 @09:33AM (#11580245)
The primary product I work on limits (on-screen) results to 10k results (after any filtering) regardless of page size. Aside: However, this was based on our most complicated queries at the time, which have since been simplified.