Changelog History
Page 3
-
v6.0.0 Changes
March 11, 2020๐ The changelog below is a summary of the all of the preview releases.
โ Added
- ๐ New gRPC .NET client added.
- The ability to filter reads by regex or prefix for both stream name and event type.
- ๐ New options for certicates. Can be provided as PKCS, public/private key pair and windows store.
- Introduction of a liveness health check at
{server_address}/health/live
. - ๐ Improvements to projection writes.
- Read-only replica. A node that will not partake in elections and is non promotable. Started with the
--read-only-replica
argument - The ability to resign master using
{server_address}/admin/node/resign
. - โ Added in the ability to set node priority with
{server_address}/admin/node/priority/{priority}
.
๐ Changed
- ๐ Change of cluster role names from master/slave to leader/follower.
- ๐ Both client and server have been moved over to .NET Core.
๐ Deprecated
- ๐ ATOM and TCP are being deprecated. These can be re-enabled with
--enable-external-tcp
and--enable-atom-pub-over-http
. - ๐ Clone nodes have been deprecated and replaced with read only replicas. Can be re-enabled using
--unsafe-allow-surplus-nodes
โ Removed
- ๐ Support for Event Store server on macOS.
- Undocumented projection selectors.
- The requirement for mono.
๐ Security
- 0๏ธโฃ TLS is enabled by default for internal node communication. Can be disabled by
--disable-internal-tls
. - 0๏ธโฃ All external HTTP is HTTPS by default.
-
v6.0.0-preview3
March 11, 2020 -
v6.0.0-preview2
January 20, 2020 -
v6.0.0-preview1
December 16, 2019 -
v5.0.8
March 30, 2020 -
v5.0.7
March 17, 2020 -
v5.0.6
February 19, 2020 -
v5.0.5 Changes
November 15, 2019Event Store 5.0.5 Changelog
๐ Features
#2051 - ( Core Database and Client ) Bug fix: ConcurrentQueueWrapper can return negative count
-
v5.0.4 Changes
November 06, 2019 -
v5.0.3 Changes
November 03, 2019Event Store 5.0.3 Changelog
๐ Bug Fixes
#1971 - ( Core Database ) Persistent Subscriptions: Always remove completed events from all connections to prevent outstanding messages from building up in the connection queues
#1991 - ( Core Database ) Make the connection queue size threshold configurable. There are scenarios where a client might run into the maximum connection queue size. A likely scenario where this might occur is when a client is overwhelmed by a large number of events being ingested into Event Store and then being delivered to a subscription.
#1998 - ( Core Database ) Persistent Subscriptions: Retry the load checkpoint read if the read expires.
#1990 - ( Core Database ) We have fixed a bug in our intermediate index cache.