4 ms·
No kidding. Without details, it really sounds like the author is a bit clueless. He mentions the lack of joins, but doesn't say a word about Mapreduce. "Mongo
by mayank 13y ago
No kidding. Without details, it really sounds like the author is a bit clueless.
He mentions the lack of joins, but doesn't say a word about Mapreduce.
"MongoDB needs to walk the index from the beginning to the offset..." You don't "walk an index". It's an index.
"Too many databases" sounds a little suspicious. Why not add an indexed field to partition records?
Complaining about a lack of schema, transactions and triggers? Really? Did you read the docs at all before starting?
MongoDB is not without its problems, but friend, I think you wanted either Postgres or Hadoop.
- PavlovsCat 13y agoYou don't "walk an index". It's an index 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.
- shane42 13y agoThe problems with pagination are explained better on this SO post: http://stackoverflow.com/questions/7228169/slow-pagination-over-tons-of-records-in-mongo http://stackoverflow.com/questions/7228169/slow-pagination-o... Mongo docs used the "walk" terminology
- mayank 13y agoNot sure what you're getting at. "Walk" usually means a sequential scan. An index is sorted, so you can binary search.
- PavlovsCat 13y agoSee 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.
- monstrado 13y agoIt 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.