[SERVER-16298] db.system.namespaces not registering existing collections Created: 24/Nov/14  Updated: 25/Nov/14  Resolved: 25/Nov/14

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: 2.8.0-rc0
Fix Version/s: None

Type: Bug Priority: Critical - P2
Reporter: Norberto Fernando Rocha Leite (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-16225 Emulate query results for system.name... Closed
Operating System: ALL
Steps To Reproduce:

db.a.insert({'a':1})
show collections
db.system.namespace.find()

show collections shows the created collection
system.namespaces.find() does not

Participants:

 Description   

Running mongod-2.8.0-rc1-pre- I find that the db.system.namespaces collection is not showing existing collection:

nair(mongod-2.8.0-rc1-pre-) MongoMKDB> show collections
blobs               4.433MB / 4.113MB
nair(mongod-2.8.0-rc1-pre-) MongoMKDB> db.system.namespaces.count()
0
nair(mongod-2.8.0-rc1-pre-) MongoMKDB> db.system.namespaces.find()
Fetched 0 record(s) in 0ms
 

I found this through running some tests with the java driver (and other drivers do the same) who pings the database on system.namespaces to find all existing collections.



 Comments   
Comment by Norberto Fernando Rocha Leite (Inactive) [ 24/Nov/14 ]

Yes, this is wt.
Closing.

Comment by Ramon Fernandez Marina [ 24/Nov/14 ]

If this is with WT I think this is expected behavior – see SERVER-16225. If this is with mmapv1 I'm not able to reproduce with 2.8.0-rc1.

Generated at Thu Feb 08 03:40:36 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.