What's New in v2.1.0-beta.20180924

September 24, 2018

Get future release notes emailed to you:

Downloads

SQL language changes

  • CHANGEFEEDs will retry, rather than abort, in certain cases when failing to emit to a sink. #30157
  • The new ALTER ... CONFIGURE ZONE statement can be used to add, modify, reset, and remove replication zones, with support for placeholders ($1, etc.) and for multiple executions. The new SHOW ZONE CONFIGURATION statement can be used to view existing replication zones. Clients should use these SQL statements instead of the cockroach zone sub-commands, which are now deprecated and will be removed in a future version of CockroachDB. #30173
  • Added the 2.0 value for both the distsql session setting and the sql.defaults.distsql cluster setting, which instructs the database to use the 2.0 auto behavior for determining whether queries are distributed or run through the gateway node. #30209

Command-line changes

  • The various cockroach zone sub-commands are now deprecated and will be removed in a future version of CockroachDB. Clients should use the SQL interface instead via SHOW ZONE CONFIGURATION and ALTER ... CONFIGURE ZONE. #30173
  • Improved the output of cockroach node status to include separate is_available and is_live columns. #30268
  • The cockroach debug zip command now also collects heap profiles that were generated and stored when there was high memory usage #30281

Bug fixes

  • The ON DELETE CASCADE and ON UPDATE CASCADE foreign key actions no longer cascade through NULLs. #30122
  • Fixed the evaluation of <tuple> IS NOT NULL and <tuple> IS NULL comparison operations involving a non-null constant tuple to return true or false rather than NULL. #30184
  • Fixed the occasional improper processing of the WITH operand with IMPORT/EXPORT/BACKUP/RESTORE and common table expressions. #30198
  • Fixed the return type of an array built from the results of a subquery to be elementType[] rather than tuple{elementType}[]. #30237
  • Fixed a panic that was occurring when the cost-based optimizer was disabled and an array built from the results of a subquery was used in the WHERE clause of an outer query. #30237
  • Fixed a panic that occurred when not all values were present in a composite foreign key. #30153
  • Transaction size limit errors are no longer returned for transactions that have already committed. #30304

Performance improvements

  • Avoided unnecessary allocations when parsing prepared statement placeholders. #30299
  • 1PC transactions now avoid writing transaction record and intents when pushed due to reads at a higher timestamp. #30298

Contributors

This release includes 46 merged PRs by 20 authors.


Yes No

Yes No