Fw: [mongodb-user] MongoDB 4.2.0-rc0 is released

16 views
Skip to first unread message

Satoshi OKANO

unread,
Jun 7, 2019, 12:34:19 AM6/7/19
to mongo...@googlegroups.com
岡野です。

4.2.0-rc0が来たようです。

> In addition, new driver-side helpers make it easier for you to develop transaction retry logic in your app.

このあたりは期待したいですね。4.0はイマイチ書きづらい感じでしたので。

Forwarded by Satoshi OKANO <s-o...@nri.co.jp>
----------------------- Original Message -----------------------
From: "'Kelsey Schubert' via mongodb-user" <mongod...@googlegroups.com>
To: mongodb-...@googlegroups.com, mongod...@googlegroups.com, mongodb-dev <mongo...@googlegroups.com>
Date: Wed, 5 Jun 2019 12:33:24 -0400
Subject: [mongodb-user] MongoDB 4.2.0-rc0 is released
----

MongoDB 4.2.0-rc0, the first release candidate of MongoDB 4.2, is out and
is ready for testing. This is the culmination of the 4.1.x development
series, and includes many exciting new features. Here are some of the
highlights:
Transactional Data Integrity

Distributed Transactions: Support for multi-document ACID transactions
<https://docs.mongodb.com/master/release-notes/4.2/#distributed-transactions>
is now extended to sharded clusters.

Global Point In Time Reads: Snapshot read isolation in 4.2 guarantees your
apps are always returned a consistent view of data, even when the data is
distributed across a sharded cluster, and as it is being modified by other
operations.

Large Transactions: By representing transactions across multiple oplog
entries, you can now write more than 16MB of data in a single ACID
transaction.

Transaction Diagnostics and Error Handling: Transactions metrics are now
written to system logs, helping you optimize application performance. In
addition, new driver-side helpers make it easier for you to develop
transaction retry logic in your app.

Mutable Shard Key Values: You can now update one or more shard key values
to modify the placement of a document in a cluster using a single,
all-or-nothing ACID transaction (subject to the existing 60 second default
execution time).
Complex Queries & Real-Time Analytics

On-Demand Materialized Views: Outputs from aggregation pipeline queries can
now be merged with existing persisted result sets whenever you run the
pipeline, giving you materialized views that are refreshed on-demand.

Wildcard indexes: You can now define a filter that automatically indexes
matching fields, sub-documents, and arrays in a document
<https://docs.mongodb.com/master/reference/method/db.collection.createIndex/#create-a-wildcard-index>,
providing much simpler schema design for polymorphic document structures.

More Expressive Update Language: You can now use the aggregation pipeline
to construct update operations based on values in other fields, with all
updates performed in a single atomic operation.

New Mathematical Operators: New aggregation operators and expressions:
MongoDB 4.2 adds support for new regex aggregation operators, a dozen new
mathematical expressions for rounding
<https://docs.mongodb.com/master/reference/operator/aggregation/round/#exp._S_round>
and trigonometry
<https://docs.mongodb.com/master/release-notes/4.2/#aggregation-trigonometry-expressions>,
as well as current time expressions like $$NOW to reduce the amount of code
you need to implement back in your app tier.
Resilience and Scalability

New Online Index Builds: As fast as foreground builds, they don’t block
service to the app

10x Faster stepDown and Keepalive Connections: As soon as you issue a
stepDown command, the MongoDB primary now immediately initiates an election
rather than wait on the secondaries to call it. After the stepDown,
existing read connections on the former primary are kept open, and are only
re-established on the new primary once reads have completed and their
associated cursors closed.

Storage Node Watchdog: Adding to existing network heartbeats
<https://docs.mongodb.com/manual/core/replica-set-elections/index.html#heartbeats>,
the Storage Node Watchdog
<https://docs.mongodb.com/manual/administration/monitoring/#storage-node-watchdog>
can be used to monitor MongoDB’s underlying filesystems and initiate an
automated failover if any of them becomes unresponsive. This allows the
cluster to automatically self-heal in the face of a wider range of failure
conditions.

Faster Initial Sync: You can now add new nodes to a replica set 15%
faster, while also reducing load on the source replica.

Zstandard Compression: MongoDB 4.2 adds support for Zstandard compression
<https://docs.mongodb.com/master/release-notes/4.2/#zstd-availability>,
providing up to 55% storage savings compared to snappy, with lower CPU
overhead than Zlib.
Enterprise Security

Improved Auditing Performance: We’ve refactored internal locking within the
Auditing plugin, resulting in a 3x performance improvement.

Multi-Certificate Authority and Forward Secrecy TLS Encryption: Separate
Certificate Authorities can now be configured for inbound and outbound
encrypted connections to a MongoDB Atlas cluster. In-flight encryption also
now supports the latest TLS cipher suites offering Forward Secrecy.

Zero Downtime Certificate and Keyfile Rotation: You can now change your
keyfiles and X.509 certificates without having to take down your cluster.

MongoDB 4.2 Release Notes <http://docs.mongodb.org/master/release-notes/4.2>
| Changelog
<https://jira.mongodb.org/issues/?jql=project%20in%20(SERVER%2CTOOLS%2CWT)%20AND%20resolution%3D%27Fixed%27%20and%20(fixversion%20in%20versionMatch(%224.1.%5B0-9%5D%22)%20or%20fixVersion%20%3D%204.2.0-rc0)>
| Downloads <https://www.mongodb.com/download-center>

-- The MongoDB Team

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.

For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/CALYkeJGD0fUt%3D3XfBMCSsPa_UUr%2BRYscisvfk%3DKTzN%2B5t2U%2BtA%40mail.gmail.com.

--------------------- Original Message Ends --------------------

Reply all
Reply to author
Forward
0 new messages