What's new in MongoDB 4.2.1
Nov 14, 2019
- SERVER-37768: Platform Support: Add Community & Enterprise Debian 10 x64
- SERVER-37772: Platform Support: Add Community & Enterprise RHEL 8 x64
- SERVER-41506: Track metrics associated with a node calling an election
- SERVER-41499: Track number of elections called for each reason in serverStatus
- SERVER-42518: Wildcard index plans miss results when the query path has multiple subsequent array indexes
- SERVER-42856: Transactions with write can be sent to the wrong shard
New in MongoDB 4.0.9 (May 13, 2019)
- SERVER-38949: Incorrect index bounds for {$ne: [“String”]} query
- SERVER-38984: Attach IDs to users
- SERVER-39178: Negotiate SCRAM mechanism in MongoURI::connect()
- SERVER-40333: Only clone collection options once for each shard on shard collection
New in MongoDB 4.0.6 (Feb 19, 2019)
- SERVER-37778: Platform Support: Add Community & Enterprise Ubuntu 18.04 (zSeries)
- SERVER-37777: Platform Support: Add Community SLES12 (zSeries)
- SERVER-37775: Platform Support: Add Community RHEL7 (zSeries)
- SERVER-39180: Wrong initial chunk owner shard can be selected when sharding non-empty collection with pre-created zones
- SERVER-32146: Log slow oplog entry application
- SERVER-38293: Make listDatabases understand collection privileges
- SERVER-38887: Mongo.getDBs() does not correctly inspect privileges
New in MongoDB 4.0.5 (Jan 8, 2019)
- SERVER-36437: The dbstats command should lock the database in MODE_IS instead of MODE_S
- SERVER-37182: Different values when referencing whole object vs. a field of that object after $arrayToObject
- SERVER-37200: $match stage following $listSessions not working against mongos
- SERVER-37557: Add startup warning about enableMajorityReadConcern and usage of arbiters
New in MongoDB 3.6.0 (Dec 27, 2017)
- MongoDB 3.6 makes it easier than ever to work with data in the most natural, efficient, and frictionless way possible. In short, MongoDB helps you go faster when building and scaling apps. Key 3.6 features include:
- Change streams enable you to build reactive web, mobile and IoT applications that can view, filter, and act on data changes as they occur in the database. Whenever data is changed in MongoDB, downstream systems are automatically notified of the updates in real time. Change streams provide an easy and efficient way to build reactive, event driven apps.
- Retryable writes move the complexity of handling transient systems failures from the application to the database. Instead of you having to implement masses of custom, client-side code, MongoDB automatically retries write operations using exactly-once semantics.
- With Schema validation, using syntax derived from the proposed IETF JSON Schema standard, we’ve extended the document validation capabilities originally introduced in MongoDB 3.2. Now, DevOps and DBA teams can define a prescribed document structure for each collection, down to the level of individual fields within nested arrays. And you’re able to tune this as you need: lock the schema down, open it up, apply it to a subset of fields – whatever you need for each app or stage of your project.
- Binding to localhost by default: with MongoDB 3.6 all MongoDB packages across all platforms refuse all external connections to the database unless explicitly configured otherwise by the administrator. Combined with new IP whitelisting support, administrators can configure MongoDB to only accept external connections on approved IP addresses. These enhancements greatly reduce the risk of unsecured MongoDB instances unintentionally being deployed into production.
- Aggregation enhancements support more expressive queries, giving you faster access to data-driven insights. MongoDB’s document data model allows you to model entities in the same way you represent them in code - as complete objects - so you don't need to worry about JOINs. But for analytics it’s useful to join data across multiple collections. We introduced left outer equijoins in MongoDB 3.2, but now we are expanding this with a more powerful $lookup operator to support the equivalent of SQL subqueries and non-equijoins. MongoDB's Connector for BI, which enables MongoDB to be used as a data source in SQL-based analytics and data visualization tools, takes advantage of these enhancements to deliver higher performance, with more analytic operations pushed natively to the database.
- MongoDB Atlas is the best way to run MongoDB in the public cloud. MongoDB 3.6 is available as a fully managed service on Atlas, including important new features to support global applications, and with automated scalability and performance optimizations.
- Cross-region replication allows Atlas clusters to span multiple cloud provider regions, maintaining continuous availability in the event of geographic outages, and providing optimal customer experience by distributing data closer to users. Atlas now also supports automatic scaling for storage associated with a cluster, making it easier for you to manage capacity. The new performance advisor continuously highlights slow-running queries and provides intelligent index recommendations to improve performance.
New in MongoDB 3.4.6 (Jul 10, 2017)
- Issues fixed:
- SERVER-27347: Only close idle cached cursors on the WiredTiger ident that is busy.
- SERVER-29618: $geoWithin in aggregation pipeline after $lookup and $unwind returns incorrect results.
- WT-3362: Cursor opens should never block for the duration of a checkpoint.
New in MongoDB 3.4.1 (Jan 15, 2017)
- SERVER-27124 Disallow readConcern:majority reads on pv0
- SERVER-27201 $graphLookup triggers null pointer dereference
- SERVER-27207 Find on view with sort through mongos may incorrectly return empty result set
- SERVER-27213 Two $match stages combine incorrectly, yielding incorrect results.
- SERVER-27300 Disallow indexing of BSONType::Symbol with a non-simple collation
- SERVER-27210 3.4.0 mongo shell unable to connect using MongoURI with "ssl=true"
- SERVER-27271 rolesInfo command raises System.InvalidOperationException : Duplicate element name 'roles'.
- SERVER-26870 Sometimes collection data file is not removed even though collection is dropped
- TOOLS-1541 Support exporting views
New in MongoDB 3.0.6 (Aug 27, 2015)
- Improvements to WiredTiger Stability SERVER-19751, SERVER-19673, and SERVER-19573.
- Fixed issue with the interaction between SSL and Auditing. SERVER-19538.
- Fixed issue with aggregation $sort on sharded systems SERVER-19464.
- All issues closed in 3.0.6
New in MongoDB 3.0.4 (Jun 18, 2015)
- Fix missed writes with concurrent inserts during chunk migration from shards with WiredTiger primaries: SERVER-18822
- Resolve write conflicts with multi-update updates with upsert=true with the Wired Tiger Storage engine: SERVER-18213
- Fix case where secondary reads could block replication: SERVER-18190
- Improve performance on Windows with WiredTiger and documents larger than 16kb: SERVER-18079
- Fix issue where WiredTiger data files are not correctly recovered following unexpected system restarts: SERVER-18316
New in MongoDB 3.0.0 (Mar 6, 2015)
- 7-10x Better Performance:
- The new WiredTiger storage engine in MongoDB 3.0 delivers 7-10x greater throughput for write-intensive applications with more granular document-level concurrency control. This translates to massive performance gains with less hardware for write-heavy projects such as your next IoT, customer data management, social, and mobile apps.
- Up to 80% Less Storage:
- MongoDB now supports native compression, allowing you to reduce your physical storage footprint by up to as much as 80%. You have the added flexibility to choose between different compression algorithms to optimize for performance and storage efficiency, depending on your apps needs.
- With more granular concurrency control and built-in compression, MongoDB 3.0 lets you simplify your architecture, allowing you to do far more with less hardware.
- Reduce Operational Overhead By Up to 95%:
- Ops Manager is the best way to run MongoDB. This solution makes routine tasks as easy as pushing a button and eliminates previously manual and time consuming tasks involved in managing MongoDB. You can now deploy, monitor, back up and scale MongoDB with ease.
- Pluggable Storage Optimized For Your Workload:
- We understand that with an increasingly complex landscape of data-driven apps, a “one size fits all” approach to storage doesn’t cut it anymore. That’s why MongoDB 3.0 includes a pluggable storage engine API to extend the database with new capabilities.
- Low Latency Across the Globe:
- Today's leading applications are global and serve always-connected audiences that demand instant gratification. With MongoDB, you can now easily distribute up to 50 MongoDB replicas closer to your users all over the world, reducing the effects of network latency and providing a better user experience.
- Enhancements That Make You More Productive:
- MongoDB 3.0 includes a number of operational improvements to the MongoDB Query Language as well as the tools included with the database. They include...
- Faster Loading and Export. Data can be loaded and extracted at higher speed and with greater efficiency using MongoDB’s revised multi-threaded mongoimport, mongoexport, mongodump, mongorestore and mongooplog tools.
- Easier Query Optimization. Better understand query performance with the new explain() method. It is now possible to calculate and review query plans without first running the query. The query plan can be applied to a broader set of query types, and error handling is improved.
- Faster Debugging. You now have much greater control over the granularity of log messages and specific functional areas of the server to more precisely investigate issues. You can configure which specific components of the database should be exposed for higher definition logging and add severity levels for each log message.
- Richer Geospatial Apps. With the addition of big polygon selections, MongoDB’s geospatial support is extended to include multi-hemisphere queries that can span more than 50% of the earth’s surface. For example, an airline can now run queries to identify all aircrafts that have traveled across multiple hemispheres in the past 24 hours.
- Better Time-Series Analytics. Developers can construct richer time-series analytics queries with less code using the aggregation framework’s new $dateToString operator.
- Ensure Regulatory and Internal Compliance:
- MongoDB 3.0 adds to the existing security capabilities of the database with a more robust auditing framework.
- Auditing now extends beyond capturing administrative actions (i.e. schema operations, authentication and authorization activities) to include the logging of read and write (DML) operations to the database. You can construct and filter audit trails for any operation against MongoDB without having to rely on third-party tools. 3.0 also features the introduction of role-based auditing. Auditing is available as part of MongoDB Enterprise Advanced.
New in MongoDB 2.6.7 (Jan 22, 2015)
- Decreased mongos memory footprint when shards have several tags SERVER-16683
- Removed check for shard version if the primary server is down SERVER-16237
- Fixed: /etc/init.d/mongod startup script failure with dirname message SERVER-16081
- Fixed: mongos can cause shards to hit the in-memory sort limit by requesting more results than needed SERVER-14306
- All issues closed in 2.6.7
New in MongoDB 2.6.5 (Oct 17, 2014)
- $rename now uses correct dotted source paths SERVER-15029
- Partially written journal last section does not affect recovery SERVER-15111
- Explicitly zero .ns files on creation SERVER-15369
- Plan ranker will no longer favor intersection plans if predicate generates empty range index scan SERVER-14961
- Generate Community and Enterprise packages for SUSE 11 SERVER-10642
- All issues closed in 2.6.5
New in MongoDB 2.5.5 (Feb 5, 2014)
- New:
- New write operation method for insert, update, remove
- Bug fixes:
- SNMP Agent does not start
- Add module suite support to smoke.py
New in MongoDB 2.5.4 (Jan 13, 2014)
- Add option to compact command to leave in padding
- User defined roles
- Server automatically abort queries/commands after user-specified time limit
New in MongoDB 2.4.9 (Jan 11, 2014)
- Bug fixes:
- misplaced openssl callback registration can cause crashes
- clang compiled mongo shell crashes on exit with a stack trace in v8
- logging in ~ReplicaSetMonitor() crashes
- Non-numeric expiresAfterSeconds causes bad TTL query
- Shell stops working after long autocomplete operation
- Failure to rollback usePowerOf2Sizes should not cause fatal error
- SERVER-11869 Support for non-client opTime in mongod GLE
- $where inside of projection $elemMatch causes segmentation fault
- Passing $where predicate to db.currentOp() crashes mongod
- Cannot set false setParameter options in config file
- textIndexVersion compatibility check not complete
- writeback listener may not get correct code back from ClientInfo::getLastError
- Mongos cannot do slaveOk queries when primary is down
- New sharded connections to a namespace trigger setShardVersion on all shards
- retry logic for read preferences should also apply on lazy recv() network failure
- slaveok versioning logic in mongos should also apply to read prefs
- Modifying collection options can cause restores of collection to fail
New in MongoDB 2.4.8 (Dec 5, 2013)
- Increase future compatibility for 2.6 authorization features
- Fix dbhash cache issue for config servers