[00:38:52] <Boomtime> @morf: although ->"render collections to tables" -> you know that's impossible right? documents are schemaless by default - the only table column that is assured to exist is _id, every other column might be unique per document
[00:39:52] <morf> Boomtime: well i'm not storing random data they are pretty much the same like in traditional sql dbs
[00:43:25] <shlant> hi all. can I safely ignore "The server certificate does not match the host name x" messages if I have —sslAllowInvalidHostnames set for my replica?
[00:48:04] <morf> shlant: that's for you to decide, if you know the certificate is valid and right, just for different hostname, you can imho safely ignore it
[00:48:23] <Boomtime> @morf: unfortunately, any tool which assumes your condition, wouldn't work in the general case
[00:48:35] <Boomtime> with that said, you will find some suggestions around
[00:49:11] <Boomtime> have you looked through this list? -> https://docs.mongodb.org/ecosystem/tools/administration-interfaces/#data-viewers
[00:50:15] <Boomtime> @shlant: that message is effectively telling you a man-in-the-middle attack might be going on - you are explicitly telling it you don't care - do you care?
[00:51:23] <Boomtime> crypto on the wire is not entirely useless anyway, since it will certainly stop eavedroppers and capturing after-the-fact, but your configuration won't stop more sophisticated attacks like man-in-the-middle
[00:52:16] <Boomtime> the trouble is, if you sufficiently trust your network enough to believe man-in-the-middle is not possible, then why are you using SSL?
[00:52:19] <shlant> morf: that's what I thought. As long as it's not rejecting connnections or something because of it
[00:54:13] <morf> Boomtime: yeah i get it ... i just want something that doesn't exist yet again :)
[00:56:23] <Boomtime> right, then you're all good, the options you chose reduce what would be an error, to a warning, and the connection is accepted (with regrets)
[02:51:11] <shlant> Boomtime: that's a good question. It's partly because the related app is being used to advertise the importance of privacy and partly because setting up ssl using existing certs isn't a big deal, but setting up a whole certificate issuing service will be a PITA
[03:38:15] <Boomtime> @shlant: yep, i understand - so long as you are aware of the shortfalls in security you can work towards improving it
[03:42:23] <shlant> Boomtime: for sure. Thanks for looking out :)
[11:00:19] <ondreian> anyone ever came across an error like this: MongoError: BSONObj size: -1859549040 (0x90882991) is invalid. Size must be between 0 and 16793600(16MB) First element: ?`@: ?type=-124
[15:14:13] <metame> ondreian: not sure what your query looks like that's causing the error but this might help: http://stackoverflow.com/questions/22213777/exception-bsonobj-size-286331154-0xeeeeeeee-is-invalid-size-must-be-betwee
[15:49:44] <glowdemon1> I'm trying out something like Twitter and I need to store statuses. Whenever I place a status on a webpage, it needs to show the status and the number of the status. The number needs to be an incremented ID to keep count of statuses. How would I accomplish this?
[15:50:11] <glowdemon1> Because I've read that incremented IDs are a no-go in Mongo, perhaps there are other alternatives.
[15:56:06] <metame> glowdemon1: instead of overriding the _id you can just add another field like status_id to your doc
[16:02:24] <metame> glowdemon1: to implement it with consistency you can follow the docs: https://docs.mongodb.org/manual/tutorial/create-an-auto-incrementing-field/
[16:03:42] <metame> glowdemon1: really depends on scale but using an auto-increment pattern with something as (potentially) numerous as statuses may hurt perf
[17:39:46] <diegoaguilar> Hello where can I get a compiled linux version of mongosniff
[17:56:54] <diegoaguilar> Hello, can someone please give an eye to this