Introducing MongoDB Shell in DataGrip
Hi! We’ve released the new version of the MongoDB JDBC driver, which means that DataGrip now includes support for the new MongoDB Shell out of the box. This is the result of a close collaboration between engineering teams at MongoDB and JetBrains, and we are excited to finally release it to all our users.
If you use DataGrip to work with MongoDB and Atlas, you get a console/shell experience that is 100% consistent with what you get in MongoDB’s own shell and other MongoDB developer tools.
To use the newest version of the driver, just update it in the properties window of your MongoDB data source.
All the commands that you can run in the MongoDB shell are now available in DataGrip and other JetBrains IDEs, and they work in exactly the same way as they do in MongoDB. Here’s the overview of what’s now available.
Calling up the help field works.
More methods for cursors: explain, projection, close, isClosed, hasNext, next, isExhausted, itcount, map, tailable, toArray, readPref, and readConcern.
New methods for working with collections: db.getCollectionInfos(), db.getCollectionNames(), and db.collection.remove().
You could previously create many types of BSON objects, but not all of them. This new update adds support for the ones that were missing: Date, HexData, and MD5.
Before, only two bulkWrite options were supported: insertOne and deleteOne. Now updateOne, deleteMany, updateMany, and replaceOne are supported, as well.
The readConcern and writeConcern options are supported for all commands, for example aggregate, bulkWrite, count, and others.
A known issue: collections with periods in their names cannot be used in commands, but there is a workaround:
A great fit for Atlas Data Lake
DataGrip works well with MongoDB deployments, whether self-managed or in Atlas. It also works with Atlas Data Lake. If you have data stored in Amazon S3 and you want to query and analyze it with MQL, you can create a Data Lake and start working with it right away.
DataGrip and MongoDB teams