MongoDB 3.2.0-rc3 is released

MongoDB
November 17, 2015
#Releases

MongoDB 3.2.0-rc3 is out and is ready for testing. This is the culmination of the 3.1.x development series.

Fixed in this release candidate:

SERVER-20164: Finish unit tests for CatalogManagerReplicaSet::addShard
SERVER-21287: $lookup should use $eq queries
SERVER-21298: rollback_index.js fails to wait for replication before continuing
SERVER-21292: replsets/remove1.js failed in replset_legacy suite
SERVER-20937: Add mode to FSM framework that drives greater amount of load on the system
SERVER-21099: Improve logging in SecureRandom and PseudoRandom classes
SERVER-20402: Add Election Failover JS tests
SERVER-21308: fsm-suite doesn’t wait long enough for the distributed lock when dropping a collection
SERVER-20867: Integrate mongobridge into ShardingTest
SERVER-21355: Coverity analysis defect 76731: Unchecked return value
SERVER-21305: Lock ‘timeAcquiringMicros’ value is much higher than the actual time spent
SERVER-21371: find_and_modify_concurrent_update.js join() is called after read
TOOLS-983: mongorestore panic when restoring a compressed archive without using –gzip

Want to test the release? Get involved in the MongoDB Bug Hunt and enter for a chance to win some prizes for your contributions.

3.2 Release Notes | Downloads | All Issues

As always, please let us know of any issues.

– The MongoDB Team

← Previous

MongoDB Authentication and Automation

MongoDB supports role-based authentication, so you can restrict access to your deployment for safety and security. Cloud Manager Automation makes enabling and managing your users easy. An important note before we begin: Authentication Settings made here apply to your entire Cloud Manager group. If you are using Automation, and it’s vital that different deployments in your group have different credentials, you will have to create a new Cloud Manager group for these deployment items and import them . Enabling Authentication If you already have authentication enabled, follow the normal importation into Automation methodolgy , especially noting the creation of a new automation-agent user, then you can skip this section and go on to the role and user management sections below. If you have an unauthenticated deployment: Click the “…” menu on your Deployment Page and choose “Authentication & SSL Settings” Click “Next” to get to the “Select Authentication Mechanisms” screen Select “Username/Password” and click “Next”. Click “Next” again to skip the SSL settings (a topic for this other post ). Now you will see the new users that will be automatically created for you. Click “Save” to create a new automation draft with your new users. Now you just have to “Review & Deploy” and “Confirm & Deploy” as normal. Beware: Clients without authentication will fail to connect after this point. Make sure your application is ready for this change. Check your drivers’ documentation on how to enable MongoDB authentication in your application. Role Management Let’s start with adding a new role: Head over to your “Authorization & Roles” tab When you click the “Add Role” button in the upper-right, you will be presented with a dialog to fill out: You can even add collection-level and other privileges if you want In my case, I’ve let my reader role also be able to do certain diagnostic actions Once the role is added, you just have to do the usual “Review & Deploy”/”Confirm & Deploy” to push this role out to your group. Once the role has been created, you can edit or remove it via the gear icon, as shown below. You can only edit custom roles, not built-in roles . Users Once you have the roles you need (if you need custom roles at all), you can start creating users. Head to your “Authentication & Users” tab Create a new user via the “Add User” button in the upper-right You can choose any custom or built-in roles you wish and enter the user’s password Once the user is added, you just have to do the usual “Review & Deploy”/”Confirm & Deploy” to push this user out to your group. Once the user has been created, you can edit or delete it via the gear. You cannot edit the built-in users for the agents. Removing Authentication Maybe you have moved your deployment into a private network and have decided to remove your authentication settings. Here’s how: Click the “…” menu on your Deployment page and select “Authentication & SSL Settings” Click “Next” to get to the “Authentication Mechanisms” screen and un-check “Username/Password” Click “Next” to skip the SSL settings, and then click “Save” When you next do a “Review & Deploy”/”Confirm & Deploy”, the Automation Agents will disable authentication. All your custom roles and users will remain cached in Cloud Manager in case you wish to re-enable authentication. You can edit them even when authentication is not enabled.

November 16, 2015

Next →

MongoDB Releases “Focus Mode” in Compass GUI

We’re excited to announce an improvement to the aggregation-building experience in MongoDB Compass. Compass already makes it easy to view and manage your MongoDB databases, and with the addition of Focus Mode you now have the option to dial in on specific stages within your aggregation pipeline. Overview MongoDB's Query API and Aggregation Pipelines enable easy retrieval and processing of data from collections. They also facilitate complex operations such as filtering, grouping, and transforming, making computation and analysis effortless. MongoDB Compass' intuitive interface simplifies the process of building aggregations by enabling developers to easily create, test, and refine aggregation pipelines, and the introduction of Focus Mode takes this a step further. When constructing pipelines, having to simultaneously view and consider multiple stages can make it challenging to analyze the impact of a specific stage, leading to increased cognitive load. Now, developers can toggle Focus Mode on stages, opening a view that focuses exclusively on the contents of the specific stage they are working on. This view can also be used to view sample input (before the aggregation stage is applied) and output (after the stage is applied) documents, aiding in the understanding, troubleshooting, and optimizing of the data pipeline. Developers can also switch between different stages by accessing a drop-down menu at the top of their screen. This makes identifying inefficiencies and optimizing performance easier, as well as providing deeper insights from the output documents for data-driven decision making. Focus Mode offers a streamlined and distraction-free environment for working with stages, improving the efficiency and precision of testing, debugging, and analyzing the impact of each stage on the data, ultimately simplifying the creation and management of pipelines. Conclusion The addition of Focus Mode is part of our continued refresh of the query and aggregation experience in Compass. These improvements are made possible thanks to the feedback of our developer community, so we encourage you to try out this new feature and let us know what you think! To learn more about Aggregation Pipeline Builder in Compass, visit our documentation .

March 21, 2023