Getting rid of temporary indexes in RavenDB

Published on 2013-2-14

I talked about RavenDB's new ability to promote and demote automatically created indexes yesterday, but what are the implications of this?

I mentioned that the process in RavenDB for managing dynamically created indexes is as thus:

Well, we now have a way of marking indexes as idle and therefore not taking up needless resources, we can remove temporary indexes entirely.

That's actually a lot of code we can remove, in fact a pile of code that I wrote over two years ago, that's kinda cool, as it means entire code-path that doesn't need maintaining any more.

Obviously we can still remove auto indexes that were only queried once or twice, but that can take part with the algorithm that marks them as idle, and to make things even better we can add some functionality to the Studio to manage these idle indexes or delete them.

Now, this still isn't as awesome as it could be, but we've laid the ground work for a pretty awesome feature, I'll talk about that tomorrow.

Why not hire me?

I am available for emergency consults, workshops, training and short-term development work anywhere in Europe

C#, JavaScript, Clojure, RavenDB, NodeJS, Architecture review.. etc

Get in touch

blog comments powered by Disqus