+972 52-548-6969
RavenDB 4.1 Release Candidate is out
time to read 1 min | 128 words
Last Friday, without much of a fanfare, we released the Release Candidate of RavenDB 4.1. This release concludes about six months of work to bring some new and awesome features to the table:
- Cluster wide transactions
- JavaScript indexes
- SQL Migration Wizard
- Distributed Counters
- RavenDB Embedded (for .Net, Python, etc)
- MongoDB & CosmosDB migration
- Results highlighting
- Subscription includes
- Explain query plan
- Explain query execution
- Query timing
- Better setup wizard and reducing deployment friction
And these are just the first dozen big features. We made a lot of improvements, supporting wild card certificate generation in the setup process, better spatial units support and a plenty of other stuff that isn’t sexy or attractive on its own but adds up to a major jump in what you can do with RavenDB.
Comments
Updating from 4.0 to 4.1 RC - can we just replace the binaries?
Judah, Yes, you can replace the binaries, but be aware that we upgrade the internal structure as we do so. In other words, you cannot go back
Are there any plan on installer like RavenDB 3.5? A bit of scary to replace binaries or delete previous binaries and copy over new one.
I did mistake few weeks ago when update my local development environment. Which accidentally deleted database folder. Which cause me to re-setup everything. I didn't do replace just worry there are binary that suppose to be removed.
Jason, The typical way to avoid that is to setup the db directory outside of the binaries folder. We don't do this by default because it complicates the user's life in many cases (running multiple ravendb instances that will use the same path, for example. Installers are complex, especially now that we run on multiple platforms. Probably the easiest way to get what you want it to use docker with an attached volume.
Cool. I will try that out. Thanks
Comment preview