-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
ALL
I started up my mongod with the --notablescan option. I had the twitter tweets collection from the training coarse loaded, but I'm sure this will work with any collection.
Table scans with predicates generate errors, but table scans without predicates do not:
> db.tweets.find(
{'user.followers_count':1000});
error:
> db.tweets.find().skip(1000).limit(1);
{ "_id" : ObjectId("4e55766a89c942db6fdd8ddc"), "text" : "@LiLMAMAs0FLi yhu qoht
ah aim ma?", "in_reply_to_status_id" : NumberLong("22815133901"), "retweet_coun
t" : null, "contributors" : null, "created_at" : "Thu Sep 02 18:13:21 +0000 2010
", "geo" : null, "source" : "<a href=\"http://www.sidekick.com\" rel=\"nofollow\
">T-Mobile Sidekick</a>", "coordinates" : null, "in_reply_to_screen_name" : "LiL
MAMAs0FLi", "truncated" : false, "entities" : { "user_mentions" : [
], "urls" : [ ], "hashtags" : [ ] },
"retweeted" : false, "place" : null, "user" :
, "favorited" : false, "in_reply_to_user
_id" : 105635017, "id" : NumberLong("22819521200") }
Plain db.tweets.find(); works also, but scrolls off the screen, so I couldn't cut-and-paste it as above.
- duplicates
-
SERVER-2222 notablescan mode neglects to fail some table scan queries
- Backlog