+972 52-548-6969
RavenDB 2.5 is out, and a happy New Year
About six weeks ago, we actually released RavenDB 2.5 to the world. It was build 2666. I decided to do something a bit different, and do a silent launch. In other words, We released it, let the people in the mailing list know about it, but we didn’t make a big fuss about it.
Now we have a new build, 2700 (which isn’t going to evoke… certain issues for some people), and we want to make as much noise as possible. Because RavenDB 2.5 is out, and it is really cool.
Here are some of the new stuff:
- Dynamic Reporting
- Result Transformers
- Scripted Index Results
- Unbounded Streams support
- MSI Installer
- Index directly to memory
- Smarter query optimizer
- Idle indexes, index priorities and locked indexes
And that is just a taste.
In fact, we are going to do a Webinar about how cool RavenDB 2.5 is on Monday. You can register using the following link: https://www2.gotomeeting.com/register/551636514
And, of course, go and get the latest RavenDB from our site.
And have a great New Year, everyone. We will be off for the Holiday until next Monday…h
Comments
Congrats Oren! Just wondering if the "EsentOutOfSessionsException" problem got already fixed in the 2700 ot not, and if so in which way (the double context + disposal of "myContext" way or the Lazy way).
Anyway thanks and congratulations again, awesome stuff!
njy, The problem there is solved (it happened almost 2 months ago), and it was solved in the way shown in the post.
Oh, I see: I thought it was recent stuff, since the post outlining the problem came out yesterday.
Anyway, taking a look at the code: calling CreateEsentTransactionContext() creates an EsentTransactionContext and a new Session (also IDisposable), which may or may not be heavier than just creating a Lazy. Btw I also noticed that since you previously do a TryGet before that, the overhead may be minor, and also you would not having Lazy instances around for each key in the ConcurrentDictionary. Dunno, just something to think about.
Perhaps the indexing documentation could be amended / augmented with an overview of the differences between typical relational database indexing and indexing in RavenDB which would address the tendency of folks new to RavenDB to 'over-index', creating many indexes which could be collapsed.
Ayende, it would be great if you mention in your posts which version of ravendb is effected - regarding confusion with bug posts etc.
Thanks again for your blog.
J Healy, We actually handled that better now, and we will merge the indexes automatically.
So what time zone is IST? First Google Calendar set my registration up as 7:30 am US Eastern time (apparently using Indian Standard Time for IST). That wasn't right, so looked up other possibilities for IST and found Ireland Standard Time. All indications are that means noon U.S. Eastern time. Try to connect to the webinar a few minutes before noon EST and it says it is waiting for the presenter. A few minutes after noon I try connecting again and it says the webinar is over.
I've signed up for the Sept. 24th webinar and it also uses the mysterious IST time zone. Exactly what is the IST time zone offset from GMT for that webinar? Maybe I won't miss that one too!
Comment preview