> you no longer have to manually specify cache sizes for tables to prevent running over memory and into swap

I'm really glad you're addressing this. Does this auto-sizing apply to RethinkDB's memory usage in general? The last time I tried using it on a small VPS, I set my table's cache size really low, but I still ran out of memory whenever I ran queries on a large table.

Definitely looking forward to secondary index export/migration and to upgrades without the export-import cycle.