Changelog History
Page 1
-
v2.4.1
August 13, 2020 -
v2.4.0
March 31, 2019 -
v2.4.0-beta
March 31, 2019 -
v2.3.7
August 15, 2019 -
v2.3.6 Changes
July 23, 2017๐ Bug fix release
Notes
๐ This is the first release of RethinkDB since October 2016. The RethinkDB project has joined the Linux Foundation. This release is brought to you by volunteers from the Open RethinkDB team. The RethinkDB source code is now licensed under an ASLv2 license.
Compatibility
๐ On 32-bit platforms and on Windows (64 and 32 bit), RethinkDB 2.3.6 servers should not be mixed with servers running RethinkDB 2.3.3 or older in the same cluster. Doing so can lead to server crashes when using the web UI or when accessing the
logs
system table.โฌ๏ธ On 64-bit platforms, RethinkDB 2.3.6 servers can be mixed with older RethinkDB 2.3.x servers in the same cluster. We recommend that you run a mixed-version cluster only temporarily for upgrading purposes.
๐ No migration is required when upgrading from RethinkDB 2.3.x. Please read the [RethinkDB 2.3.0 release notes][release-notes-2.3.0] if you're upgrading from an older version.
๐ Changes
- Server
- Improved the compatibility of the web UI with Chrome 49 and Edge (#5878, #5426, #5300) -- @danielmewes
- Fixed a crash caused by unwanted connections (#6084) -- @danielmewes
- Fixed a crash caused by recreating indexes with active changefeeds (#6093) -- @danielmewes
- Sizes passed to
sample
are now bound by the array size limit (#6148) -- @AtnNn - Fixed a crashing bug in the implementation of the
interleave
argument tounion
(#6139) -- @AtnNn - Fixed a crash caused by
eqJoin
of system tables when using theuuid
identifierFormat
(#6108) -- @nighelles - Fixed a bug that caused
r.match('')
to return wrong results (#6241) -- @AtnNn - Miscellaneous regression fixes and code improvements by @srh and @VeXocide
- Fixed argument order in pretty-printed queries in the jobs table (#6240) -- @AtnNn
- Packaging
๐ Official Downloads: https://rethinkdb.com/docs/install/
- Server
-
v2.3.6-windows
July 17, 2017 -
v2.3.6-0RC2
July 12, 2017 -
v2.3.6-0RC1
February 07, 2017 -
v2.3.5 Changes
August 29, 2016๐ Bug fix release
Compatibility
๐ On 32-bit platforms and on Windows (64 and 32 bit), RethinkDB 2.3.5 servers should not
be mixed with servers running RethinkDB 2.3.3 or older in the same cluster. Doing so can lead to
๐ server crashes when using the web UI or when accessing thelogs
system table.๐ On 64-bit platforms other than Windows, RethinkDB 2.3.5 servers can be mixed with older
RethinkDB 2.3.x servers in the same cluster. We recommend that you run a mixed-version cluster
โฌ๏ธ only temporarily for upgrading purposes.โฌ๏ธ No migration is required when upgrading from RethinkDB 2.3.x. Please read the
๐ RethinkDB 2.3.0 release notes if you're upgrading from an older version.๐ Bug fixes
- Server
- Improved the efficiency of the on-disk garbage collector to reduce the risk of
excessive file growth (#5923) - Improved the latency of read queries under heavy write loads (#6072)
- Fixed a bug that could cause the server to crash with a deserialization error
or to stop completing any table reads (#6033) - Fixed a bug in the implementation of the
interleave
option of theunion
command,
which could potentially lead to results being generated in the wrong order (#6041) - Fixed a bug in the batch handling of the
fold
and multi-streammap
commands,
that would stop results from being generated correctly if these commands were
applied to a changefeed (#6007) - Fixed an issue that could cause proxies to remain listed in the
connected_to
field of theserver_status
table, even after they had disconnected (#5871) - Fixed the detection of non-deterministic conflict functions in the
insert
command
(#5842) - Improved the Raft election timeout logic to avoid infinite Raft election loops (#6038)
- Improved the response time when reading from the
table_status
system table (#4589) - The server no longer logs the message
Rejected a connection from server X since one is already open
when trying to connect
to itself (#5456) - Fixed a bug that could cause an
Uncaught exception
server crash if a TLS-encrypted
connection was closed during a certain connection stage (#5904) - Fixed a bug in
merge
that could causer.literal
objects to remain after themerge
and be stored in a table (#5977) - On Windows: Fixed a bug in the
r.http
command that resulted in decoding issues (#5924) - On Windows: RethinkDB now binds TCP ports exclusively (#6008)
- On Windows: No longer print an error to the log whenever a connection attempt fails
(no issue #) - Fixed a build issue that caused system libraries to not be found during
make
on
OpenSUSE (#2363)
- Improved the efficiency of the on-disk garbage collector to reduce the risk of
- JavaScript driver
- Java driver
- Python driver
- The
asyncio
loop type is now available when using the driver from a Python .egg
file (#6043)
- The
- ๐ Ruby driver
- Fixed a rounding issue with time objects (#5825)
Contributors
Many thanks to external contributors from the RethinkDB community for helping
us ship RethinkDB 2.3.5.- Arve Seljebu (@arve0)
- Ben Sharpe (@bsharpe)
- Brian Chavez (@bchavez)
- Dan Wiechert (@DWiechert)
- mbains (@mbains)
- QianJin2013 (@QianJin2013)
- Raman Gupta (@rocketraman)
- Server
-
v2.3.5-windows
August 27, 2016