ScyllaDB Enterprise 2019.1.11

The ScyllaDB team announces the release of ScyllaDB Enterprise 2019.1.11, a production-ready ScyllaDB Enterprise patch release. As always, ScyllaDB Enterprise customers are encouraged to upgrade to ScyllaDB Enterprise 2019.1.11 in coordination with the ScyllaDB support team.

The focus of ScyllaDB Enterprise 2019.1.11 is improving stability and bug fixes. More below.

Related Links

• Get ScyllaDB 2019.1.11 (customers only, or 30-day evaluation)
• Upgrade from 2019.1.x to 2019.1.11
• Upgrade from 2018.1.x to 2019.1
• Upgrade from ScyllaDB Open Source 3.0 to ScyllaDB 2019.1
• Submit a ticket

New Features

• ScyllaDB Enterprise Docker: a new --io-setup N command line option, which users can pass to specify whether they want to run the scylla_io_setup script or not. This is useful if users want to specify I/O settings themselves in environments such as Kubernetes, where running iotune is problematic. #6587

Fixed issues in this release are listed below, with open source references, if present:

• Install / Upgrade (RPM): ScyllaDB Enterprise metapackage does not install correct version of scylla-enterprise-conf package #5639
• CQL: Impossible WHERE condition returns a non-empty slice #5799
• Stability: Counter write read-before-write is issued with no timeout, which may lead to unbounded internal concurrency if the enclosing write operation timed out. #5069
• CQL: Using CQL functions Max and Min on data type inet/blob/list/map/set/time/tuple/udt/column returns unexpected result #5139
• CQL Role Based Access Control (RBAC): MODIFY permission is required on all materialized views in order to modify a table. #5205
• CQL: Range deletions for specific columns are not rejected #5728
• Compression: Internode, on the wire, compression is not enabled based on configuration #5963
• Stability: Open RPC stream connection when the reader has no data generate errors: stream_session - stream_transfer_task: Fail to send to x.x.x.x:0: std::system_error (error system:99, connect: Cannot assign requested address)
• Stability: Staging SSTables are incorrectly removed or added to backlog after ALTER TABLE / TRUNCATE #6798
• Stability: Issuing a reverse query with multiple IN restrictions on the clustering key might result in incorrect results or a crash. For example:
  CREATE TABLE test (pk int, ck int, v int, PRIMARY KEY (pk, ck));
SELECT * FROM test WHERE pk = ? AND ck IN (?, ?, ?) ORDERED BY ck DESC;
  #6171

30 Jul 2020