[SERVER-4636] Insert operations to collections system.profile and system.namespaces finished successful, but new data didn't appeared there Created: 06/Jan/12  Updated: 11/Jul/16  Resolved: 17/Jan/13

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: 2.0.2
Fix Version/s: None

Type: Question Priority: Major - P3
Reporter: Uladzimir Mihura Assignee: Unassigned
Resolution: Done Votes: 0
Labels: epam, namespace, profiling
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows 7 x64, Windows Server 2008 R2 x64, Ubuntu 11.04 x64


Issue Links:
Related
Participants:

 Description   

Insert operations to collections system.profile and system.namespaces finished successful, but new data didn't appeared there. I think it would be good if an exception would be thrown here.

$ mongo
MongoDB shell version: 2.0.2
connecting to: test
> use newdb
switched to db newdb
> db.getCollectionNames()
[ ]
> db.tmp.insert({"field": "value"})
> db.getCollectionNames()
[ "system.indexes", "tmp" ]
> db.system.namespaces.find()
{ "name" : "newdb.tmp" }
{ "name" : "newdb.system.indexes" }
{ "name" : "newdb.tmp.$_id_" }
> db.system.namespaces.insert({"name": "newdb.newtmp"})
> db.system.namespaces.find()
{ "name" : "newdb.tmp" }
{ "name" : "newdb.system.indexes" }
{ "name" : "newdb.tmp.$_id_" }
 
 
> db.setProfilingLevel(2)
{ "was" : 0, "slowms" : 100, "ok" : 1 }
> db.system.profile.insert({"field": "value"})
> db.system.profile.find()
{ "ts" : ISODate("2012-01-06T13:30:46.592Z"), "op" : "insert", "ns" : "newdb.system.profile", "millis" : 0, "client" : "127.0.0.1", "user" : "" }



 Comments   
Comment by Eliot Horowitz (Inactive) [ 17/Jan/13 ]

Was fixed in 2.2

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