Re:Why MongoDB is a bad choice for storing our scraped data
by shane42 on Tuesday May 14, 2013 @10:20AM
(#5704993)
The problems with pagination are explained better on this SO post:
http://stackoverflow.com/questions/7228169/slow-pagination-o...
Mongo docs used the "walk" terminology
Re:Why MongoDB is a bad choice for storing our scraped data
by mayank on Tuesday May 14, 2013 @10:21AM
(#5705000)
Not sure what you're getting at. "Walk" usually means a sequential scan. An index is sorted, so you can binary search.
Re:Why MongoDB is a bad choice for storing our scraped data
by PavlovsCat on Tuesday May 14, 2013 @10:41AM
(#5705138)
See other reply. If the docs say MongoDB "walks", it's hilarious to complain that someone obviously didn't read the docs for saying "walk", too.
Re:Why MongoDB is a bad choice for storing our scraped data
by monstrado on Tuesday May 14, 2013 @10:27AM
(#5705046)
It looks like they went with HBase for the replacement which means they can scan an index range, keys are in lexicographical order, so it makes it pretty easy to scan over a series of data with a single RPC call.
If you have an address book, you don't have to walk through the city to find an address, but you do have to look through your address book in some way or other. Of course, you can have an index of the index ("C starts at page 7"), but then you have to look through the index of the index.