[14:14:18] <cezary_zukowski> How to store JSON in Mongo? Should I use String type in schema or another type?
[14:47:34] <edrocks> cezary_zukowski you can store it as a regular document. Every driver I've used takes json in as bson and converts for you
[14:47:51] <edrocks> I wouldn't store it as a string it kinda defeats the whole purpose
[14:48:40] <edrocks> unless you want to treat it as some opaque data you have no access to from the database. IE it'd just be GET or SET operations on some key storing that json. Might be useful for user uploaded json or some caching scenarios
[14:48:57] <edrocks> I'd store it as bytes if you are going to do that though
[16:30:48] <peteski> Anyone in here use MongoDB with the Java driver? I'm having some issues even following the install/quick tour stuff with the latest versions. Had to upgrade the package from the old async driver and it's become a bit chaotic for me. If there's anyone around I can sound off, that might be helpful for my mental health
[16:32:22] <peteski> this is what I'm talking about: http://mongodb.github.io/mongo-java-driver-reactivestreams/
[23:25:52] <kairoz> I'm trying to do a rolling restart on one of my MongoDB replica sets (running 3.2.21-3.12). However, when a mongod instance restarts, it doesn't receive the correct uptime information from other hosts -- instead, it thinks that the other hosts have uptimes slightly shorter than it does, and therefore it won't sync from anyone.
[23:26:21] <kairoz> Is there any way to hard adjust the uptime that a node thinks it has so that I can tell it to be a SECONDARY node and respect its elders?
[23:33:11] <kairoz> (eventually the node just started behaving itself... so, I'm confused, but it's not as big a deal as I thought it was initially)