Migration: Server Breaking Changes
The features listed on this page were available in former RavenDB versions.
In RavenDB 7.1.x, they are either unavailable or their behavior is inconsistent with their behavior in previous versions.
RavenDB incorporates NLog as its logging system
- RavenDB's logging system has changed; the server now incorporates the NLog logging framework and writes all log data through it.
- One of the changes that NLog brings to RavenDB is the richer set of logging levels, visible right away through Studio's admin-logs view.
- Read more about Nlog in the dedicated article.
If you migrate to RavenDB7.xfrom an earlier version, please read the section related to NLog in the migration page.
Removed obsolete properties
The following properties are no longer in use and have been removed in RavenDB 7.1.
-
ServerOptions'sAcceptEulaproperty is no longer used.
Please useLicensing.EulaAcceptedinstead.// Removed
bool AcceptEula -
The
MemoryInfoResultstruct no longer includes these classes:-
MemoryUsageIntervals// Removed
sealed class MemoryUsageIntervals -
MemoryUsageLowHigh// Removed
sealed class MemoryUsageLowHigh
-
Filtered vector search behavior
In RavenDB 7.0:
When combining a vector search with a filtering condition using AND, the filter was applied after the vector search completed within the NumberOfCandidates limit.
As a result, increasing NumberOfCandidates was often necessary, since the filter could discard many of the retrieved candidates.
In RavenDB 7.1:
The filter is now integrated into the vector search process.
RavenDB automatically ensures that enough results matching both the vector similarity and the filtering condition are found, without requiring manual adjustments to NumberOfCandidates.
Learn more in How filtered vector search works.