The article you are looking for does not exist in the chosen language.
You were redirected to the main page of java documentation.
We hereby welcome you into the RavenDB Documentation.
Feel free to explore the sizeable world of our premier NoSQL database.
[Backup]
Fixed an issue that restoring from incremental backup with atomic guard, a tombstone could be handled before creating the document[Cluster Transactions]
Improved performance of cluster-wide transactions[Cluster Transactions]
Fixed the restore of a database with cluster transactions[Cluster]
Improved performance of updating database values by using separate semaphores for database record changes and value changes[Debug]
Added method to delete document by Etag[Expiration & Refresh]
Added an option to specify max number of items to process in a single run[Indexing]
Fixed unhandled cases in Index Merger. Added better error handling.[Monitoring]
Exposed alerts and notifications via /databases/*/notifications
endpoint[Querying]
Fixed translation of DateTime.MaxValue
to JS date when building RQL with JS projection[Querying]
Fixed count, distinct, and paging for very specific cases of collection queries[Querying]
Fixed the detection of index staleness which could result in returning stale results in specific scenarios[Replication]
Added authorization check for the legacy replication for indexes[.NET]
Updated to .NET 7.0.18[Bulk Insert]
Fixed a possible NRE in the heartbeat timer
[Cluster Transactions]
Removed a legacy check if Cluster Transactions are supported[Indexing]
Exposed referenced collection in index statistics[Cluster]
Avoid logging expected cluster exception[Cluster]
Fixed the failover mechanism for cluster transactions[Cluster]
Using SemaphoreSlim
instead of a blocking Monitor.TryEnter
as the cluster lock to prevent potential ThreadPool starvation[Cluster]
Fixed an edge case of NRE in ClusterStateMachine
when adding a database[ETL]
Stopping an ETL tasks in an async fashion to avoid holding the cluster lock[Indexing]
Fixed incorrect staleness status due to unprocessed document tombstones after the replication[Indexing]
Fixed handling of field names extraction for boosted fields in JavaScript index definition[Licensing]
Making sure the license verification check will be executed when running as Windows Service[Revisions]
Fixing an issue that Enforce revisions configuration was skipping on docs when passing multiple collections[Subscriptions]
Fixed an issue with missing metadata on subscriptions with revisions enabled[Subscriptions]
Foxed a task connection status when getting subscription ongoing task by name[ThreadPool]
Doubling the minimum workers of ThreadPool in the default configuration[Voron]
Fixed occasional failures in loading the storage report[.NET]
Updated to .NET 7.0.17HandleClusterDatabaseChanged()
Storage.Temp
configuration option for temporary directoryMySqlConnector
in
clauseWhatChanged()
did not return old value for RemovedField on DictionaryRequestExecutor
instancesHiLoIdGenerator
while a custom AsyncDocumentIdGenerator
convention was set[JavaScript Indexes]
Fixed regression introduced in 5.4.113 which made that date fields indexed by JavaScript indexes got different format so queries could not find old results. If an index is affected (has a date field) then the reset is required in order to recover.
[Counters]
Fixing the allocation size for a counter group name when purging counter tombstones
[Subscriptions]
fixed issue with concurrent subscription not picking up appropriate state when connecting