yugabyte/yugabyte-db v2.1.3

v2.1.3 (Apr 09 2020)

on GitHub

YSQL Changes

• [YSQL] Parallel queries across tablets for SELECT COUNT|MIN|MAX|SUM (*|col_id) FROM. #3624
• [YSQL] Fixed bug when processing PgsqlConditionPB::operands::column_id. #3837
• [YSQL] IndexScan returns all rows when there is no match. #3896
• [YSQL] Partial support for operator families, ALTER OPERATOR and ALTER EXTENSION. #2711
• [YSQL] Handle transaction conflict status in case of parallel read operations. #3991
• [YSQL][YCQL] Wrong results when using DocDB reverse scans with paging #4004
• [YSQL] Flush buffered operations before calculating query time. #3696

YCQL

• [YCQL] Send proper error when we query system.peers_v2 table. #3862

System improvements

• Implement paging for index backfill. #3879
• Rename indices to indexs in the context of index-backfill. #3901
• Cleaner error reporting from process main. #3876
• Fix determining the oldest SST file for intent cleanup. #3917
• Fix the TS UI transactions link. #3922
• Fix transaction status resolution with old peer version. #3916
• Add nodiscard attribute to Status class. #3918
• [docdb] Deregister callback for common mem trackers from root mem tracker in destructor of vector. #3750
• First phase of transaction aware snapshot. #1032
• [cdc] Fix data races in CDC Poller. #3771
• [YSQL] Fix for PgGate shutdown race on shutdown_done flag. #3779
• Initial multi node yugabyted version. 2057
• Enable checksum verification for meta blocks of encrypted files. #3974
• Batch copy table operations that happen during create database. #3743
• yb-admin: flush_table_by_id, compact_table_by_id #3814
• [docdb][ysql] Reuse iterators during txn conflict resolution. #3521
• Persist backfilling timestamp across master failures. #3611
• Relax requirement on number of log segments in QLTransactionTest.PreserveLogs. #3989
• Fix encryption format for newly created files. #3976
• Move remote bootstrap call to OpenTablet to the threadpool. #3012
• Support the ability to fetch the oldest timestamp record that is more recent than a specified time. #4019
• A flag for veryfing meta block checksums. #4023
• Stop cleaning intents SST files if previous file was not actually deleted. #3917
• Fix MakeFuture utility. #3781
• Restore transaction aware snapshot. #1032
• Fix demo destroy behavior with Python 2.7.5. #3993
• Adding health check for the Tserver. #3540
• Don't block remote bootstrap service during session init. #4035
• YBClient sbould wait for all sync operation to complete upon shutdown. #3989
• Inherited permissions shouldn't replace granted permissions in the client's cache. #4062
• Fix race condition on ParseTree::stale_. #3083
• Handle RPC register failure in TransactionStatusResolver. #4064
• Handle tablet not running in /transactions page. #4071
• Propagate history cutoff from leader. #1032
• Allow yb-admin to work with any non-leader master. #4000
• Transaction aware snapshot persistence. #1032
• Optimize returning results from tserver to postgres. #3926
• Allow tracing recent operations in MvccManager. #4108
• Persist ALTER ROLE changes to disk. #4105
• colocation: cache db colocated in postgres #4101

Platform

• Fix edit flow to show encryption at rest flags properly. #3910
• Add support for disabling readonly users. #3794
• Add API to get client certificate. #3984
• Create GCP provider with shared VPC and allow specifying subnets per region. #3383
• Update AWS price info && stop auto-running update script.
• Remove devops subnetId requirement when specifying a VPC when creating GCP provider.
• Add node ip to all created universes
• Omit master servers from being counted toward total node/pod count. #4009
• Update master selection logic. #3999
• Prevent data move if there is no data to move. #4046
• UI to set region-subnet mapping when creating GCP provider for existing VPCs. #3381

Note

Prior to 2.0, YSQL was still in beta. As a result, 2.0 release includes a backward incompatible file format change for YSQL. This means that if you have an existing cluster running releases older than 2.0 with YSQL enabled, then you will not be able to upgrade to version 2.0+. Export from old cluster and import into a new 2.0+ cluster is needed for using existing data.