Why don't any Mongodb Admin UI's allow batch updates?

The most recent versions of MongoDB will yield regularly during the mass update, but you're still talking about syncing gigabytes of data to the disk for one simple change. If this multi-update results in a few minutes of work, you will see timeouts on your client and random messages in the log, but there's no way to know the process until it's done.

  Database administrator training   Apr 3, 2024   106  Add to Reading List

I cannot speak to each one specifically. What I can say is that the "multi" update matches up a little funny with most management interfaces. You basically have to add this really dangerous little switch to the update command.

Remember, running a multi-update can absolutely destroy your DB performance. MongoDB has only one write lock per DB. So if you issue some command that updates 5GB worth of documents that command will interfere with everything else that is going on.

The most recent versions of MongoDB will yield regularly during the mass update, but you're still talking about syncing gigabytes of data to the disk for one simple change. If this multi-update results in a few minutes of work, you will see timeouts on your client and random messages in the log, but there's no way to know the process until it's done.

I honestly recommend against multi-updates on production data. Instead, issue a query for the IDs you want to update and batch out updates in packs of 100 or 500. This way you can monitor progress and quit the job if something is going wrong.

Do I have to create my own Admin UI for my app?

Generally you do, regardless of whether or not the Mongo Admin app has the features you want. That's just good practice, avoid having your QA and your ops team reading the various DBs directly.

But specific to Mongo, one of big hurdles you'll find with a straight viewer is that all of the field names are shortened (or should be because long field name take extra space). So reading the DB directly is not necessarily the panacea you would hope for.

You'll also notice all of the viewers have this structure problem because not everything is a table, but not everything is a compactly displayed in JSON. If your documents contains "arrays of objects", they quickly become unreadable inside of the admin UIs.

Fortunately, several of the admin tools are available as open source. So if you're really just missing one feature, you should be able to add it.