[00:56:38] <tpae> it created bunch of empty arrays that goes from usage.0 ~ usage.121026
[00:56:49] <tpae> thus increasing my db usage by many folds
[00:57:01] <tpae> what's the best way to handle this..?
[01:04:53] <tpae> ok.. it turns out i created usage field as an array
[01:05:03] <tpae> i changed it to an object and it works
[01:37:46] <asdfn> Hi. A have a question. I know that ObjectID in mongo is 12-byte binary string. Does it mean that representation of this in string is always 24 character length?
[11:04:52] <syskk> how to do a case insensitive search in MongoDB? my query right now is { $or : [ { id : diet_id } , { label : diet_id } ] } label should be case insensitive
[11:53:34] <urbann> I will try to read a bit about this, thanks for your hins!
[12:28:44] <preinhei_> Derick: could you clarify something for me? I'm not sure if Mongo::connect() should be returning true on success, or simply not throwing an exception. http://www.php.net/manual/en/mongo.connect.php
[12:38:33] <Derick> preinhei_: it can throw an exception
[12:38:49] <Derick> but, you shouldn't (have to) run connect() yourself
[12:42:57] <preinhei_> At least one iteration of the driver returned that connect -> true was being deprecated
[12:43:12] <preinhei_> Is it just going to always connect?
[12:44:37] <Derick> no, connect = true/false still works
[12:44:47] <Derick> we probably undeprecated it :-)
[12:44:55] <Derick> also, I would wait until 1.3RC1 is out
[12:45:07] <Derick> we are still working on making safe-ness on by default
[12:45:46] <preinhei_> [Sun Oct 28 01:14:52 2012] [error] [client 24.246.57.214] PHP Deprecated: Mongo::__construct() [<a href='mongo.--construct'>mongo.--construct</a>]: The 'connect' option is deprecated and will be removed in the future in /var/www/api.wheresitup.com/libraries/lithium/data/source/MongoDb.php on line 259
[13:52:28] <Derick> ralph___: yes, than you have a problem :-)
[13:52:28] <lucian> i'm having trouble with a nested or. mongo won't use an index for something like {$and: [{$or: [...]}, {foo: "bar"}]}. is there some alternative?
[13:52:55] <Derick> why do you need an $and? It's the default
[13:53:03] <mbrown> Thanks for the help Derrick and Gargoyle
[13:53:12] <Gargoyle> The mongo approach is very elegant and diplomatic, but I miss the "Samuel L. Jackson, Motherfucker" feeling of using a STONITH setup! :D
[13:53:38] <lucian> Derick: you mean {$or: [...], foo: "bar"} ?
[13:57:07] <Gargoyle> Are there any downsides to using MongoBinData()? or more specifically, any pitfalls to gzipping and entire subdoc that never gets searched?
[13:57:58] <lucian> Derick: something like this https://gist.github.com/78b89c6929965ff78030
[14:01:47] <Derick> lucian: compound index on {y : 1, read: 1 } ought to be used
[14:08:49] <lucian> Derick: shouldn't an optimised see both those queries as equivalent?
[14:08:52] <Derick> mitsuhiko: and I'm sure we'll improve the one we have in the future if we can
[14:09:06] <Derick> lucian: yes, for the query it doesn't matter - it does matter how you set the compound index though
[14:09:10] <Gargoyle> Derick: If we don't need sub-meter resolution (or anywhere near it), how big is the ipact of specifying the number if bits for a 2d index?
[14:09:27] <Derick> Gargoyle: it's storage size mostly then
[14:09:28] <lucian> Derick: it matters here. $and [ $or ] scans more than the one without $and
[14:14:17] <lucian> yeah, the one without $and does use the index
[14:15:33] <Gargoyle> lucian, Derick, Butting in on your convo… does the y:1 bit have to come first in the find() query if it's first in the compound index?
[16:13:59] <TecnoBrat> Morning all, question about the new TTL based collections
[16:14:20] <TecnoBrat> I have a collection with a date field already, and we do some manual cleanup of it nightly
[16:14:30] <TecnoBrat> however, we may have old stuff hanging around
[16:14:53] <TecnoBrat> if I add the index in 2.2 to make it TTL based, how aggressive is the cleanup going to be?
[16:15:16] <TecnoBrat> is it going to try to delete it all instantly, or is it going to slowly delete them as it catches up
[16:15:51] <TecnoBrat> I just don't want a massive locking / IO spike / slowdown because of enabling it, otherwise I'll try to manually clean it up first
[16:22:57] <TecnoBrat> Also, "ct" is what I want to add the TTL index on. I already have other indexes like: '{ "s.0" : 1, "f.0" : 1, "paid" : 1, "ct" : -1 }' .. the docs say you can't create it on a field that already has an index. Does this qualify? Or does it mean if I've indexed ONLY the "ct" field I would have to remove that index first
[16:23:14] <TecnoBrat> Also ... since this is an index, I assume its treated as such for queries
[16:38:10] <jawr> if i have a collection with documents that containt uid's, how can i get a results back with the sum of various fields
[17:37:11] <NodeX> in general does anyone do it in here?
[17:41:00] <spacemonkey> I've seen auto-complete with Elastic Search on hundreds of thousands of documents, but that's about it. Not sure if that is "large" for you though.
[18:00:09] <doxavore> In MongoDB 2.0.7, I'm seeing it periodically lock up completely. I can't seem to catch something going on in db.serverStatus, but monogstat shows almost all counts go to 0, then it comes back with locked% over 500
[18:01:14] <doxavore> iowait hangs between 0 and 5 or 10%, but otherwise the server is responsive
[18:02:09] <TecnoBrat> doxavore: are you using M/R which merges into another collection?
[18:02:45] <TecnoBrat> I saw this exact behaviour on the final step of a M/R which has a merge into a collection, its the final save that caused it
[18:03:18] <doxavore> TecnoBrat: no M/R, but we are using gridfs
[18:03:30] <doxavore> (which I can't replace for something else fast enough)
[18:08:16] <jaimef> does it make sense to set vm.swappiness to 0 if mongo mmaps everything?
[18:25:59] <lucian> Derick: if you don't mind me bothering you again, i've found a case where i can't use an implicit and https://gist.github.com/78b89c6929965ff78030#file_or%20query.mongo
[18:35:01] <jrxiii> Well, can anyone here confirm that db.coll.find().addOption(16) will make the cursor timeout unlimited
[18:38:25] <jrxiii> for those who care addOption(16) will make a cursor never timeout: http://www.mongodb.org/display/DOCS/Mongo+Wire+Protocol#MongoWireProtocol-OPQUERY
[20:43:53] <mediocregopher> we're running version 2.0, if we do something like this: db.artistEvents.find({ $query: { arid: 1239926 }, $orderby: { _id: -1 } }).explain() our index doesn't get used, but if we do db.artistEvents.find({ arid: 1239926 }).sort({ _id: -1 }).explain() the index does get used
[20:45:05] <mediocregopher> according to http://www.mongodb.org/display/DOCS/Mongo+Query+Language these two queries should be the same, but it seems like they're not. our index looks like this: {