MongoDB 2.4 Compatibility

This page is a (todo) list of features/improvements in MongoDB 2.4, with their statuses w.r.t. inclusion in TokuMX. The basis for this list is MongoDB 2.4 Overview.

Developer Productivity

• Aggregation Framework refinements....
  • significant performance improvements
    • fixed in #517 (1.3.0)
  • additional support for binary data
    • fixed in #517 (1.3.0)
  • support for $geoWithin and $near geospatial queries
    • not needed until we add geospatial indexes
  • improved string concatenation with the new $concat operator
    • fixed in #517 (1.3.0)
  • and improved date calculation semantics.
    • fixed in #517 (1.3.0)
• Geospatial enhancements
  • support new use cases with support for polygon intersection queries (with $geoIntersects),
  • support for GeoJSON, and an improved spherical model.
• Text search
• New =$setOnInsert= update operator supports specifying fields to add only on insert and upsert operations.
  • fixed in #279 (1.3.0)

Ease of Operations

• Hashed indexes and shard keys provide simple, even distribution for reads and writes.
  • fixed in #24 (1.0.0)
• New serverStatus metrics including a working set analysis tool makes capacity planning easier for operations teams.
  • these changes don’t work with the tokumx storage system, we have alternative analysis tools (see db.engineStatus())
• More control for operators with the ability to terminate indexing operations with automatic resource cleanup.
  • all DDL operations, including index builds, are transactional and are therefore cleaned up automatically when terminated

Improved Performance

• V8 JavaScript engine offers better performance and concurrency with JavaScript based actions including those using the $where query operator as well as mapReduce and eval.
  • fixed in #517 (1.3.0)
• Improvements to count provide dramatically faster count operations. Counting is now up to 20 times faster for low cardinality index based counts.
  • fixed in #284 (1.1.0)
• Significant optimizations to =$elemMatch= when using a multi-key index.
  • fixed in #543 (1.3.0)

More Robust Security

• Role-Based privileges allow organizations to assign more granular security policies for server, database and cluster administration.
  • fixed in #527 (1.3.0)
• Kerberos authentication mechanism in MongoDB Enterprise.