v1.3.1 Release Notes

v1.3.1 Release Notes

Released July 31, 2019.

Downloads

Binaries

Docker

docker pull yugabytedb/yugabyte:1.3.1.0-b16

File Format Change

NoteThis version includes a backward incompatible file format change for YSQL. This means that if you have an existing cluster with YSQL schema, then you will not be able to connect to the YSQL database after upgrading to this version.

There are two ways to address the above note.

If you don’t care about preserving your existing data, then delete your cluster, and create a newcluster with 1.3.1.
If you want to continue using your existing data, then please save your data (in the form ofSQL statements), delete the cluster, create a new cluster with 1.3.1 and then load the previously saved data.

YSQL Changes

[YSQL] Fix error in nextval_internal retry.#1783
[YSQL] Support bulk inserts for COPY FROMcommand.#1590
[YSQL] Support for Triggers andExtensions.#1156
[YSQL] Simplify gflags enabling YSQL.#1691
[YSQL] Support NULLS LAST for SELECT.#1734

System Improvements

Extra cleanup of intents of aborted transactions to prevent repeated logmessages.#1722
Cleanup checkpoints on startup.#498
Unified yb::RandomAccessFile androcksdb::RandomAccessFile.#1661
Clear Pending Delete State on RPCFailure.#424
Do not crash yb-master process if we fail to find a namespace when listingtables.#1716
Allow consecutive master restarts tosucceed.#1074
Change soft memory limit handling.#1437
Use log prefix in MvccManager.#1835
Fix handling timeout of a local call in theservice.#1866
Fixed TS crash due to NULL name in the PTBindVarobject.#1821
Add /tables view to tablet server ui.#1830
Add ability to avoid using the compaction thread pool forflushes.#1874
Tablet leader tracking at catalogmanager.#1881
Allow in memory erase of intents.#1240
Fix assignment order of propagated_safe_time andpropagated.#1889
Memory monitor should not flush tablet that is alreadyflushing.#1880
Fixed potential race condition in memory-basedflush.#1859