DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Translating OData Queries to MongoDB in Java With Jamolingo
  • Cutting P99 Latency From ~3.2s To ~650ms in a Policy‑Driven Authorization API (Python + MongoDB)
  • Isolation Level for MongoDB Multi-Document Transactions (Strong Consistency)
  • Building a 3D WebXR Game with WASI Cycles: Integrating WasmEdge, Wasmtime, and Wasmer to Invoke MongoDB, Kafka, and Oracle

Trending

  • YOLOv5 PyTorch Tutorial
  • Java String Format Examples
  • Evolving Spring Boot APIs to an Event-Driven Mesh
  • How to Set Up and Run PostgreSQL Change Data Capture
  1. DZone
  2. Data Engineering
  3. Databases
  4. MongoDB 3.1.7 is Released

MongoDB 3.1.7 is Released

As a reminder, 3.1.7 is a development release and is not intended for production use. The 3.1 series will evolve into 3.2, which will be for production.

By 
Francesca Krihely user avatar
Francesca Krihely
·
Aug. 26, 15 · News
Likes (1)
Comment
Save
Tweet
Share
6.1K Views

Join the DZone community and get the full member experience.

Join For Free

MongoDB 3.1.7 has been released. As a reminder, 3.1.7 is a development release and is not intended for production use. The 3.1 series will evolve into 3.2, which will be for production.

New/fixed in this release:

  • clusterManager role does not have permission for adding tag ranges

  • $sort stage in aggregation doesn’t call scoped connections done ()

  • Truncating a capped collection may not unindex deleted documents in WiredTiger

  • Seg Fault on cloneCollection (specifically gridfs)

  • Excessive memory allocated by WiredTiger journal

  • Fatal error calling createIndex with 2dsphere

  • MMap memory mapped file address allocation code cannot handle addresses non-aligned to memory mapped granularity size

  • Mongo shell should report that subprograms exited with non-zero exit code if they die

As always, please let us know of any issues.

– The MongoDB Team

MongoDB

Published at DZone with permission of Francesca Krihely. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Translating OData Queries to MongoDB in Java With Jamolingo
  • Cutting P99 Latency From ~3.2s To ~650ms in a Policy‑Driven Authorization API (Python + MongoDB)
  • Isolation Level for MongoDB Multi-Document Transactions (Strong Consistency)
  • Building a 3D WebXR Game with WASI Cycles: Integrating WasmEdge, Wasmtime, and Wasmer to Invoke MongoDB, Kafka, and Oracle

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook