Riak TS Release Notes

Released July 5, 2016.

This is a bugfix release addressing the Data Loss bug in Riak TS 1.3.0.

Product Advisory

The default configuration for handoff.ip caused vnodes marked for transfer during handoff to be removed without transferring data to their new destination nodes. A mandatory change to configuration (riak.conf) mitigates this issue for OSS TS 1.3.0 users. While not all users were impacted by this issue, we recommend that all 1.3.0 users upgrade to 1.3.1.

Please see the product advisory for more information.

Bugs Fixed

Riak TS 1.3.0 Release Notes

Released May 4, 2016.

Riak TS 1.3.0 is open source! In addition to becoming OSS, version 1.3.0 introduces a broad range of new functionality including: an HTTP API, additional SQL commands, and relaxed key restrictions. It also includes Multi-Datacenter (MDC) replication for our Enterprise users.

We’ve also added AWS AMI support. You can find instructions for installing Riak TS on AWS here.

New Features

  • Riak TS is now open source. You can find the source code here!
  • The HTTP API is a development tool added for development and debugging purposes. It is ideal for quick prototyping efforts, and provides API calls for accessing Riak TS data over HTTP.
  • Our supported SQL commands have expanded to include WITH and INSERT. The WITH clause makes creating a TS table even easier, and INSERT provides another way to add data to your TS table.
  • The relaxed key restrictions mean the family and series keys are no longer required, which makes TS table schemas more flexible, and makes customizing the data you store and how you store even easier.
  • TS now supports MDC replication on TS tables. At this time, MDC support in TS does not include AAE fullsync. To use MDC, you will need to create your TS tables in your clusters and then configure MDC.
  • Riak TS now offers integration with PHP and .NET clients.

Additions

Changes

  • AWS AMI is now available. You can find instructions for installing Riak TS on AWS here. [PR #89]
  • riak shell has had several changes: the command record (which includes result) has been added, optional debugging has been added to exceptions, and SQL commands are allowed to span multiple lines. [PR #23]
  • Several changes have been made to facilitate rolling upgrades/downgrades in future releases:
    • The DDL compiler has been updated to facilitate rolling upgrade/downgrade functionality in future releases. [riak_ql PR #115]
    • On startup, the Riak node will walk through the riak_kv_compile DETS table and force a recompile, which will help facilitate rolling upgrade/downgrade functionality in future releases. [PR #1377]
    • The version that DDLs were compiled with will be stored in the dets table. [PR #1377]
    • The DDL compiler’s version is registered as a capability. [PR #1377]
  • elevelDB has been updated to pull in levelDB version 2.0.15. [eleveldb PR #184]
  • node_package has been updated to version 3.0.0 to address a security issue in which arbitrary root access was possible for a local user that had direct access to the Riak account. [PR #820]
  • module_info calls have been removed from riak_core_coverage_fsm:init() to speed up small queries. [PR #829]

Bugfixes

  • [Issue #29/PR #111] The quantum time period was not validated correctly. Validation of the partition key has been added to ensure only one quantum (if any) is specified during table creation, as specifying more than one causes errors.
  • [PR #1372] A bug manifested when using ‘>’ with a right side value one less that the quanta boundary.
  • [PR #1377] Fix DETs to accomodate downgrades.
  • [PR #1354] Negation of an aggregate function returned an error, but is now allowed.

Compatibility

Riak TS is compatible with the following:

  • RHEL/CentOS 6
  • RHEL/CentOS 7
  • Ubuntu 12.04 LTS
  • Ubuntu 14.04 LTS
  • Debian 7 (development only)
  • OS X 10.8+ (development only)
  • AWS Marketplace

Known Issues

  • AAE must be turned off.
  • Riak Search is not supported for TS data.
  • HTTP API security is not supported. Security checks are included in the code path, but the permissions are not registered with riak_core, so enabling security means disabling any TS functionality. [code]
  • Quanta with a ‘0’ or negative integers are not supported and will cause errors.