11–17 of 17 posts
From the FAQ: We recommend RethinkDB servers have at least 2GB of RAM Why does it needs so much memory?
I really like Rethink, but are there easy to use hosting services for it? Like ElephantSQL or Mongolabs.
There's a fairly major breaking change for a minor version bump.
I don't think there are actually any breaking changes. The release notes say "includeInitial" is breaking, but I think all of your existing application code will continue to run the same if you upgrade RethinkDB. It's just that new code using includeInitial will fail on old versions of RethinkDB.
Earlier quoted context omitted.
I don't think there are actually any breaking changes. The release notes say "includeInitial" is breaking, but I think all of your existing application code will continue to run the same if you upgrade RethinkDB. It's just that new code using includeInitial will fail on old versions of RethinkDB.
In 2.1 some changes commands included an initial value. Now none do unless you add the flag. If you depended on that behavior, your app could break.
From the FAQ: We recommend RethinkDB servers have at least 2GB of RAM Why does it needs so much memory?
The article describes how RethinkDB uses memory to reduce disk access and process queries, as well as how to reduce its memory usage with `--cache-size`.
There's a fairly major breaking change for a minor version bump.
Feature releases (e.g. 2.1, 2.2) include new features and do break compatibility on occasion (so we can quickly introduce new behavior). Any breaking changes are well-documented in the release notes[1], so you can have a smooth upgrade path.
Minor releases (e.g. 2.1.1, 2.1.2) do not have breaking changes, only bugfixes and minor improvements.
I just opened an issue so we can document this more clearly: https://github.com/rethinkdb/docs/issues/948