RethinkDB 2.2: atomic changefeeds, parallel scans, improved runtime

Re:RethinkDB 2.2: atomic changefeeds, parallel scans, improv... by bryanlarsen on Thursday November 12, 2015 @05:34PM (#10556648)

There's a fairly major breaking change for a minor version bump.

[ Parent | on HN ]

Re:RethinkDB 2.2: atomic changefeeds, parallel scans, improv... by mglukhovsky on Thursday November 12, 2015 @06:44PM (#10557013)

We maintain a stable LTS release (v2.0) for those who cannot tolerate breaking changes.

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

[1] https://github.com/rethinkdb/rethinkdb/releases

[ Parent | on HN ]

Re:RethinkDB 2.2: atomic changefeeds, parallel scans, improv... by mikemintz on Thursday November 12, 2015 @05:40PM (#10556696)

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.

[ Parent | on HN ]

Re:RethinkDB 2.2: atomic changefeeds, parallel scans, improv... by bryanlarsen on Thursday November 12, 2015 @05:58PM (#10556789)

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.

[ Parent | on HN ]

Re:RethinkDB 2.2: atomic changefeeds, parallel scans, improv... by mikemintz on Thursday November 12, 2015 @06:08PM (#10556852)

Thanks, I stand corrected! I always ignored initial values so I forgot about that case.

[ Parent | on HN ]