Skip to main content

Client Migration

Client migration to RavenDB 7.x​

Prior to version 7.0, our default HTTP compression algorithm was Gzip.
From version 7.0 on, our default HTTP compression algorithm is Zstd.

Version 7.0's client API ability to connect to a server depends on the server's version and on the compression algorithm the client uses.

  • Connecting your client to a server of version 6.0 or higher presents no problem.
  • But if you want to connect the client to a server of version 5.4 or earlier, you must switch the client algorithm back to Gzip for the connection to succeed.

Deploying multiple indexes is now atomic​

This change applies to the .NET client only.

Prior to version 7.0, IndexCreation.CreateIndexes retried the deployment index-by-index after a failed batch, so valid indexes were still created and the failures were reported as an AggregateException.
From version 7.0 on, IndexCreation.CreateIndexes and DocumentStore.ExecuteIndexes behave identically and the batch is atomic: if any index fails to compile, none of the indexes in the batch are created, and an IndexCompilationException naming the offending index is thrown.

If your deployment flow relied on the valid indexes being created despite one of them failing, deploy the indexes in separate calls, or call Execute on each index individually.

In this article