You are currently browsing legacy 2.5 version of documentation. Click here to switch to the newest 6.0 version.

We can help you with migration to the latest RavenDB

Contact Us Now

What's new

2.5.25023 - 2017/05/12

Server

Fix skipping documents in replication and SQL replication when there are indexes which use LoadDocument

2.5.25020 - 2016/12/22

This is an aggregated build for various fixes since the last stable

Server

[Prefetching] stability improvements,
[Replication] stability improvements and fixes,
[Indexing] compiled indexes will not longer be removed from compiled index cache,
[Configuration] added Raven/MinThreadPoolWorkerThreads,
[Configuration] added Raven/MinThreadPoolCompletionThreads,
[Configuration] added Raven/SqlReplication/CommandTimeoutInSec,
fixed performance when loading huge amount of databases at once

Client

[Indexes] enhanced deployment for indexes with empty arrays or byte enums,
fixed a race condition when both the Changes API and the Load API are trying to resolve a conflict,
fixed conflict resolution forQuery API and StartsWith API is used

2.5.25019-Hotfix - 2016/12/09

Client

Fixed a bug when conflicts aren't resolved when using the Query and LoadStartingWith API

2.5.25016-Hotfix - 2016/10/11

Server

[Configuration] Added Raven/SqlReplication/CommandTimeoutInSec setting,
[SQL Replication] Added CommandTimeout property to SqlReplicationConfig that allows to override command timeout per destination

2.5.25015-Hotfix - 2016/08/29

Server

[Server] Added config values for MinThreadCount: "Raven/MinThreadPoolWorkerThreads" and "Raven/MinThreadPoolCompletionThreads"
[Database] Fixed performance problem with multiple databases being loaded parallelly