We have just released the next stable build 2330 of RavenDB 2.0. You can find it here. This release contains a lot of bug fixes, improvements, streamlining and some interesting new stuff.
The full change log is actually here, because we found a bug in 2325 (ironically, it was a bug in how it reported its build number).
- SQL Replication script / configuration change (more below).
- More debug / visibility endpoints (user info, changes traffic, map/reduce data, etc).
- Better highlighting support.
- Spatial Search will sort by distance by default.
- Better indexing for TimeSpan values.
- Can do more Parallel Work in Map/Reduce indexes now.
- Map/Reudce indexes tune themselves automatically.
- Better Periodic Backup behavior when there is no new writes.
- Better handling of transactions during documents put with high number of referencing documents.
- Better use of alerts.
- Better float support.
- Better import/export UI.
- Can backup & restore even in the presence of corrupt / missing indexes.
- LoadDocument with map/reduce indexes cause issues.
- Allow to change the number of cached requests on the client side without NRE.
- Fixing Unique Constraints bundle with null unique properties.
- Forbidden error when running as a non admin user in the studio.
- Better support for indexing nullable properties with HasValue.
- Fixed a problem with replication of deleted documents when adding a new node in the topology.
- Support export / import with versioning bundle.
SQL Replication Breaking Changes
With SQL Replication, it became apparent that we missed a pretty big use case. Deletions.
Deletions is something that we didn’t handle, and couldn’t handle using the existing format. It was a touch call, but we decided to make a breaking change here.
Now, you need to define all the tables that you’ll be working with (as well as the order we will be writing to them). Assuming that we have a User document, and we want to replicate to Users and UsersGroups tables, we would have:
This replaced the sqlReplicate calls. Note that this is a hard breaking reset. When you upgrade, you’ll need to update all of your SQL Replication definitions (but you keep the replication state, you won’t have to start replicating from scratch).