YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
OTHER License
Bot releases are visible (Hide)
Published by ameyb over 3 years ago
docker pull yugabytedb/yugabyte:2.4.3.0-b6
[1342] Fixing the error message when the get host info call to gcp fails
[8165]Yugaware creates zombie ssh process
[8150] [8196] Fix preceding op id in case of empty ops sent to the follower
[8348] Correctly handling a failure to create a priority thread pool worker thread
Published by ameyb over 3 years ago
Yugabyte release 2.7.0 builds on our work in the 2.5 series, which fed into the 2.4 stable release. With release 2.7.0, we're planning development on a number of new features, as well as refinements to existing functionality.
Build: 2.7.0.0-b17
docker pull yugabytedb/yugabyte:2.7.0.0-b17
N/A
N/A
{{< note title="New release versioning" >}}
Starting with v2.2, Yugabyte release versions follow a new release versioning convention. The latest release series, denoted by MAJOR.ODD
, incrementally introduces new features and changes and is intended for development and testing only. Revision releases, denoted by MAJOR.ODD.REVISION
versioning, can include new features and changes that might break backwards compatibility. For more information, see Supported and planned releases.
{{< /note >}}
Published by ameyb over 3 years ago
docker pull yugabytedb/yugabyte:2.4.2.0-b45
Published by ameyb over 3 years ago
Build: 2.5.3.1-b10
docker pull yugabytedb/yugabyte:2.5.3.1-b10
7493 Menu shows 0 appended to "Upgrade Software0" when there is nothing to upgrade. When the universe is up-to-date (in other words, there are no upgrades available), the Action menu shows "Upgrade Software0". This is a cosmetic bug, and will be addressed in a future release.
Published by ameyb over 3 years ago
Published by ameyb over 3 years ago
Build: 2.5.2.0-b104
docker pull yugabytedb/yugabyte:2.5.2.0-b104
Published by ameyb over 3 years ago
docker pull yugabytedb/yugabyte:2.2.7.0-b5
Published by ameyb over 3 years ago
docker pull yugabytedb/yugabyte:2.4.1.0-b25
table_oid
already set 6678
ysql_dump
when backing up a node-to-node TLS-enabled universePublished by ameyb over 3 years ago
Data encryption in-transit enhancements:
Moving of TLS In-Transit Certificates to Cloud > Security Config
Support for Rolling restart of a universe (#6323)
Support for VMware Tanzu as a new cloud provider (#6633)
Alerts for backup tasks (#5556)
Support for Transactional tables and Cross Cluster Async Replication topology (#5779)
Support for very large transactions and stability improvements (#1923)
Displaying an entire query in the detailed view of the live queries tab (#6412)
Not returning Hashes and Tokens in API responses (#6388)
Authentication of proxy requests against a valid platform session (#6544)
Disabling of the unused API endpoint run_query (#6383)
Improved error handling for user-created concurrent backup tasks (#5888)
Performance improvements for live queries (#6289)
Pre-flight checks for Create Universe, Edit Universe, and Add Node operations for an on-premise provider (#6016)
Disabling of the unused API endpoint run_in_shell (#6384)
Disabling of the unused API endpoint create_db_credentials (#6385)
Input validation for Kubernetes configuration path (#6389)
Input validation for the access_keys API endpoint (#6386)
Input path validation for backup target paths (#6382)
Timeout support for busybox (#6652)
Enabling of CORS policy by default (#6390)
Deleting backups for TLS-enabled universes (#5980)
ALTER versions for ORM support (#4424)
SQL support improvements:
Performance improvements:
YSQL usability improvements:
YSQL statement execution statistics (#5478)
Improved raft leader stepdown operations, by waiting for the target follower to catch up. This reduces the unavailability window during cluster operations. (#5570)
Improved performance during cluster overload:
Improved performance for YCQL and many connections:
Improved DNS handling:
Improved master-level load balancer (LB) operations:
Skip loading deleted table metadata into master memory (#5122)
Critical fixes for transaction cleanup applicable to aborted transactions (observed frequently as servers reaching soft memory limit)
Main raft fixes:
Metrics reporting could be inconsistent due to regular and intent rocksdb using the same statistics object (#5640)
Various issues with the rocksdb snapshot mechanism used for backup/restore (#6170, #4756, #5337)
Fixes in the YCQL API:
Fixes in the YSQL API:
Retry on SSL_ERROR_WANT_WRITE (#6266)
Azure IaaS orchestration (in beta status):
Automatic Tablet Splitting:
Published by ameyb almost 4 years ago
Yugabyte Release Notes v2.5.1 Jan 14, 2021
[#5723] Support for custom CA signed certificates for encryption in-flight
[#5556] Add alerts capability for backup tasks
[#6010] YCQL: Cache authentication information
[#4874] YSQL: Backup for colocated databases
[#4899] YSQL: Index backfill unique indexes
[#6237] YSQL: add CREATE INDEX NONCONCURRENTLY grammar
[#5982] YSQL: Add support for CREATE TABLE/INDEX ... WITH (table_oid = x)
[#4770] YSQL: Completing feature RANGE Partitioning
Improved Clock Skew Handling
[#6370] Bump default max_clock_skew to 500ms
[#3335] Crash when too big clock skew is detected
[#5888] Better error for handling when user creates concurrent backup tasks
[#6016] Pre-flight checks for create universe / edit universe / add node operations
[#4183] Add error message for invalid ssh keys for onprem providers
[#5848] Onprem provider creation failure leaves incomplete state behind
[#5652] Improve delete universe handling for failed universes
[#6254] Allow user to input multiple GFlag entries at the same time
[#4843] New Health check for Replication status in 2dc setup
[#6268] Utility script to edit universe json from command line
[#4795] Embed http proxy within yb platform to avoid need for deploying nginx
[#5799] Delete platform code related to dev/debug package installs and EPEL repo
[#6228] Enabling Encryption-at-Rest without KMS config causes Create Universe to fail silently
[#6289] Fixed degraded performance on Live Queries tab caused by huge number of DOM nodes in rows
[#6383] Disabled unused API endpoint: run_query
[#6384] Disabled unused API endpoint: run_in_shell
[#6389] Input validation for kubernetes config path
[#6386] Added input validation for access_keys API endpoint
[#6382] Added UI validation for backup target paths
#6175: Use sudo when removing prometheus snapshots during platform backup
[#6602] Fix TLS directory while provisioning YB nodes.
[#6683] Use a timeout mechanism in cluster_health.py that is more compatible with docker's lack of zombie reaping
[#6633] Platform: rename Pivotal to VMware Tanzu, add Red Hat OpenShift cloud provider
[#6580] ycql: Log the status when statement fails for system query cache
[#6608, #6609] YCQL: Consolidate authentication error handling and messages
[YCQL][#6374] Upgrade spark-cassandra-connector version to 2.4-yb-3
#5678: [YCQL] Optimize updating non-indexed columns within indexed tables.
[#3329][YSQL] Optimized updates to reflect changes on necessary indexes only
[#5805] [YSQL] Use slots more widely in tuple mapping code and make naming more consistent
[YSQL] Clean up libpq connection code (#6481)
[#6417] [YSQL] Backport 'Skip allocating hash table in EXPLAIN-only mode'
[#6131] [YSQL] Dowgrade permission check for data directory to warning
[YSQL] Bubble up backfill error message (#6292)
[#5805] [YSQL] Don't require return slots for nodes without projection
[#5805] [YSQL] Split ExecStoreTuple into ExecStoreHeapTuple and ExecStoreBufferHeapTuple
[#5805] [YSQL] Error position support for defaults and check constraints
Improvements to 2DC x-cluster async replication
[#6169] Correctly replay write batches with external intents on bootstrap
[#6169] New format for external intents
[#6283] Fix Very Large Metric Lag for 2DC Txns
[#3522] Fix Threading Issues with CDC Consumer Writes
[#6068] Replicate Intents and Apply Messages for 2DC Txns
[#6169] Fix apply order of updated external intents records
[#4516] 2DC: Initial support for colocated databases
Improvements to Tooling
[#6589] docdb: Add option to clear placement info in yb-admin.
[#6223] master UI make hash_split more readable
[#6161] Change modify_table_placement_info to wipe read_replicas and affinitized_leaders
[#5420] ybase: Enhance YMaster admin page to display under-replicated tablets
[#1325] ybase: API for displaying YB version information
Improvements to Tablet splitting
[#4942] docdb: tablet splitting: implemented retries to post-split involved tablets for
#5937: Fixed the case when one of the tablet replicas is down during the split.
#6101 Add the flag to limit number of tablets per table
[#6424] Fix post-split compaction to be async
Improvements to core product security
[#6568] Add flag to force client certificate verification in SSL
[#6266] Replace retry counter with check that data is ready
[#6266] Retry SSL_write on SSL_ERROR_WANT_WRITE
[#6266] Fix handling SSL_write error
[#6394, #6434] docdb: Speedup system.partitions queries
[#3979] Add Transaction Cleanup to Catalog Manager Create DDLs
[#1258]: Send election request from master during table creation
[#6114] docdb: Add metrics for master YCQL system table
[#1259] Speedup DROP TABLE
[#5752] Avoid starving threadpool with run election tasks from FailureDetector
[#5755] Faster cleanup of transactions that failed to commit due to a concurrent abort
(#5996) Messenger::ScheduleOnReactor should break loop finding reactor
[#6305] Adaptive Heartbeat Reporting
[#6445] docdb: Master should rebuild YCQL system.partitions on a background thread
[#6696] Small master perf tweaks
[#6300] Install of s3cmd fails for default GCP OS image when airgapped
[#6085] Fixed the issue where master is brought up in read replica cluster
[#6416] Deletion with flag --node_ip fails for onprem universes.
[#6614] Fixed NPE with full move
[#6252] Fixed NPE on the metrics page
[#5942] Fixed an issue where release instance is not an option for a node should the install fail because of ssh access
[#6275] Fixed missing stats on Nodes page when universe has read replicas
[#6257] Updating user profile when smtp username or password are empty
[#6144] YCQL: Fix handling of tablet-lookup errors in Executor::FlushAsync
[#6570] YSQL: Use IsYBRelation instead of IsYugaByteEnabled
[#6492] YSQL Avoid memcpy() with a NULL source pointer and count == 0
[YSQL] Fix IsCreateTableDone for index backfill (#6234)
[#6318, #6334] Call InitThreading in YSQL webserver process
#6317: [YSQL] Fixed SIGSERV in YBPreloadRelCache
[#6364] [YSQL] Replace CurrentMemoryContext with GetCurrentMemoryContext for all pg_extensions
#6219] [YSQL] PRIMARY KEY index in TEMP TABLE is not checked for uniqueness
(#6284) [YSQL] Clear ALTERING when there's no alter
[#5805] [YSQL] Fix run-time partition pruning for appends with multiple source rels
[#6151] [YSQL] Handle rowmark in case of read with batch of ybctids
(#6270) [YSQL] Prevent concurrent backfill index
[#6133] [YSQL] Fix procedure with an INOUT parameter in DO block
[#6061] [YSQL] ysql_dump should consistently use quotes on column names
#6009: [backup][YSQL] Fixed incorrect column-ids in restored YSQL table if original table was altered.
#5954 [YSQL] Check transaction status after read finished
#6430 [YSQL] Refresh YBCache in case postgres clears its internal cache
#6468 [YSQL] Fix read restarts of request with paging state
[#6435] docdb: fixed handling of empty bloom filter key in the write path
[#6435] Fixed bloom filter index generation for range-partitioned tablets
[#6375] Check against TabletPeer returning null tablet pointer in
(#5641) Fix for --cert_node_filename for tservers and --enable_ysql
[#6318, #6334] Call InitThreading in YSQL webserver process
[#4150] Fix incorrect tracking of flushed/synced op id in case of Raft operation abort
(#6278) Master SEGV during LB due to null TSDescriptor
[#6353] Disable rocksdb flush on all DeleteTablet calls
[#6338] Fix crash with redis workloads and snapshot restore
[#6334] Attach/detach Squeasel threads to/from libcds using callbacks
[#6245] Fixed incorrect restored table schema if the table was altered after the backup.
[#6217] Avoid a possible assertion failure in CDSAttacher destructor in Webserver
[#6170] Shutdown status resolver before destroying it in ResolveIntents
[#6482] Fix timeout handling when getting safe time in a RF1 cluster
[#6635] Fix the wrong detection of communication failure when no operations transferred
[#6678] backup: Fix restore of colocated table with table_oid already set
Azure IaaS orchestration
No pricing information provided (5624)
No support for regions with zero Availability Zones(AZs) (5628)
Advisory on clock-skew
After commit a60a4ae00d217563cac865b3363e2c2bb8aa58ba, by default, any YB node will explicitly crash if it detects a clock skew higher than the max_clock_skew flag (default 500ms). This can be disabled by setting fail_on_out_of_range_clock_skew=false, but this could lead to consistency issues! The recommendation is that you ensure clocks are synchronized across your cluster.
Published by ameyb almost 4 years ago
Published by ameyb almost 4 years ago
Azure Cloud integration for Yugabyte Platform (in beta):
Yugabyte Platform is natively integrated with Azure cloud to simplify deploying, monitoring, and managing YugabyteDB deployments. This feature automates a number of operations including orchestration of instances, secure deployments, online software upgrades, and scheduled backups, as well as monitoring and alerting. (6094, 6020)
Yugabyte Platform operations now allow promoting a Yugabyte TServer only node to run YB-Master and YB-TServer process. (5831)
Enhanced multi-region capabilities with geo-partitioning and follower reads
The YugabyteDB 2.5 release adds row-level geo-partitioning capabilities as well as follower reads to the extensive set of multi-region features that YugabyteDB already had.
Enterprise-grade security features:
Authentication using the highly secure SCRAM-SHA-256 is now supported to limit security risks from brute force attacks and sniffing, including LDAP support for better user management and the ability to audit all database operations.
Table-level partitions
This allows users to split what is logically one large table into smaller sub-tables, using the following types of table partitioning schemes that PostgreSQL supports: range partitioning, list partitioning, and hash partitioning. Read more about table partitioning in YugabyteDB.
Event triggers
This is now supported in addition to regular table-level triggers in YSQL. While regular triggers are attached to a single table and capture only DML events, event triggers are global to a particular database and are capable of capturing DDL events. The event-based trigger framework enables detecting changes made to the data, and automating any subsequent tasks that need to be performed, which are useful in a number of use cases such as implementing a consolidated, central audit table (2379)
Simplified cluster administration:
Online rebuild of indexes
This is supported for both the YSQL and YCQL APIs. This means that new indexes can be added to tables with pre-existing data while concurrent updates are happening on the cluster. The online index rebuild process creates the newly added index in the background, and transactionally enables the index once the rebuild of all the data is completed. This feature allows flexibility of adding indexes as the application needs evolve to keep queries efficient.
Cluster execution statistics and running queries
This can be analyzed in detail, allowing administrators to gain insights into how the database is performing. The pg_stat_statements extension, which enables tracking execution statistics of all SQL statements executed by the cluster, is supported and enabled by default. Support for pg_stat_activity has also been added, which shows information related to the activity performed by each connection. Yet another useful feature in this category is the ability to view all the live queries being executed by the cluster at any point in time.
Detailed query plan and execution analysis
This can now be performed with commands such as EXPLAIN and EXPLAIN ANALYZE. These commands display the execution plan generated by the planner for a given SQL statement. The execution plan shows details for any SQL statement such as how tables will be scanned (plain sequential scan, index scan), what join algorithms will be used to fetch required rows from the different tables, etc.
yugabyte
user to belong to other user groups in Linux. (5943)min_num
replicas for even distribution of AZs across all regions. (5426)jsonb_path_query
). (5408)--ysql_sequence_cache_minval
. (6041)yb_backup.py
script for YugabyteDB version earlier than v2.1.4. (5810)RegularDB
and IntentsDB
. (5640)cdc_state
table. (5905)AreLeadersOnPreferredOnly
. (6081)50
. (5811)Published by ameyb almost 4 years ago
Yugabyte Release Notes v2.2.5 Dec 2, 2020
Published by ameyb almost 4 years ago
Yugabyte Release Notes v2.2.4 Oct 30, 2020
Yugabyte Platform operations now allow promoting a Yugabyte TServer only node to run Yugabyte Master and TServer process (5831)
Enhancements to on-prem Cloud Provider configuration
When creating onprem universes, YW will automatically run provisioning if airgap is enabled now, instead of asking the users to run the pre-provision script. Users will need to run the script only when creating universes without passwordless sudo access.
Do not fail universe creation if cronjobs can't be created for on-prem (5939)
Remove pre-provision script requirement for air-gapped installations (5929)
"Sudo passwordless" in on-prem cloud provider configuration toggle is renamed to “Manually Provision Node”
Added a new "Advanced" section in on-prem cloud provider configuration which includes
Use hostnames
Desired home directory
Node exporter settings
Pre-provisioning of ‘yugabyte’ user is supported for on-prem Cloud Provider. (YB devops script won't run create_user
if yugabyte user already exists) (6086)
Improvements to installation of Prometheus Node Exporter utility workflow (5926)
Prometheus Node exporter option is now available in the cloud configuration under advanced settings
Supports bringing your own node exporter user
UI/UX improvements for YB Platform
Add visual feedback when backup or restore is initiated from modal (5908)
Add new button for downloading root cert in Certificates page (5521)
Use the correct disk mount while calculating the disk usage of logs (5983)
Core Database
YSQL Support ROWS_PER_TRANSACTION option for COPY FROM stdin (6069)
Bug Fixes
Yugabyte Platform
[Replicated] Fixed an issue that would leave Replicated in a bad state if the network connection drops while uploading an airgap bundle, preventing the installation from proceeding. (https://release-notes.replicated.com/release-notes/2.49.0/)
Fix for the check if changing node count by AZ affects master node placement and requires a full move (5335)
Fix delete backup failure for TLS enabled universes (5980)
Universe disk usage shows up empty on the universe page (5548)
Fix for starting a YB TServer Node when another YB Master is down causes issues (5739)
Fix platform backup script for replicated installations (6130)
Core Database
[docdb] Fix a rare bug on restore which could clear more metadata than necessary (5788)
[docdb] Fix a rare race condition between transactions and snapshots that could lead to a deadlock (6170)
[YSQL] Fix an issue with setting bind address for YSQL metrics endpoint for IPv6 scenarios (4901)
[YCQL] Fix for bug with the duplicate row detection that allows a unique index to get created when the table is not unique on the index column(s) (5811)
[YCQL] Fix a bug with update and expression indexes, where an index row would get deleted if the column is updated without changing the indexed value (expression) (5898)
[YSQL] Fix OOM with \copy or COPY FROM stdin for large files (5603)
Known Issues
Yugabyte Platform
Client Certificates are not valid on download due to incorrect validity time (6118)
Tasks page reports incorrect status of failed backup (6210)
Platform Support Package Improvements
(Only applicable to Non-Replicated installations)
Yugabyte Platform
Fix for On-prem YB Platform backup fails due to file owned by root (6062)
Published by stevebang almost 4 years ago
yugabyte
user to belong to other user groups in Linux. (5943)min_num
replicas for even distribution of AZs across all regions. (5426)jsonb_path_query
). (5408)RaftConsensus
tests. (4548, 5912)--ysql_sequence_cache_minval
. (6041)yb_backup.py
script for YugabyteDB version earlier than v2.1.4. (5810)RegularDB
and IntentsDB
. (5640)cdc_state
table. (5905)AreLeadersOnPreferredOnly
. (6081)50
. (5811)Published by stevebang about 4 years ago
ALTER COLUMN
type that does not require on-disk changes #4424
COPY FROM
command syntax #2855, #5453
TRUNCATE
#5443
cron
expression shows the next run time in local browser time and the label displays that cron
supports UTC only #4709
sudo
requirement in DB backup script #5440
ORDER BY
columns exist in the table but not in chosen index #5690
UPDATE
with RETURNING
clause #5366
COPY FROM
query #2855
COPY TO
query #5205
/opt/yugabyte/release
directory does not exist #5615
Note:
Prior to v2.0, YSQL was still in beta. Upon the release of v2.0, a backward-incompatible file format change was made for YSQL. For existing clusters running pre-2.0 release with YSQL enabled, you cannot upgrade to v2.0 or later. Instead, export your data from existing clusters and then import the data into a new cluster (v2.0 or later).
Published by stevebang about 4 years ago
pg_stat_statements
extension by default. #5750
PgStatement
objects on hot path after usage to avoid memory consumption. #5374
INSERT
and UPDATE)
on transaction conflicts and avoid surfacing transaction errors to user applications. #4291
SELECT_LOCAL
, SELECT_LOCAL_TOKENS
, and SELECT_PEERS_TOKENS
) for caching. #5753
ORDER BY
columns exist in table, but not in the chosen index, and raise an error. #5690
rlimit
flags to have at-least semantics. Only change the process soft limit if it is smaller than the limit specified by the corresponding flag value. #5715
webserver_interface
to rpc_bind_address
IP/host component. #5320
yugabyted
. New env variables for YSQL (YSQL_USER
, YSQL_PASSWORD
, and YSQL_DB
) and YCQL(YCQL_USER
, YCQL_PASSWORD
, and YCQL_KEYSPACE
). (#5499
max_stale_read_time_ms
) to 60 seconds. Previously, a follower could return requested data no matter how state the data is. #5590
/tablet-servers
page) after nodes are removed from the cluster. #4759
rpc_bind_addresses
. #5634
0.8.1
. #5759
curl
requests. #5587
NOT USED
if the node is not in use. #5713
Note:
Prior to v2.0, YSQL was still in beta. Upon release of v2.0, a backward-incompatible file format change was made for YSQL. For existing clusters running pre-2.0 release with YSQL enabled, you cannot upgrade to v2.0 or later. Instead, export your data from existing clusters and then import the data into a new cluster (v2.0 or later).
Published by stevebang about 4 years ago
COPY <table> FROM <file>
to load data from a large file to a table. #5453
46f3701
so that 2.3 upgrades can proceed. #5408
Admin
, ReadOnly
, or BackupAdmin
) from the UI by an admin. Also, fix stale users list after creation or deletion of a user and disable Save buttons at Customer Profile tabs for ReadOnly
users. #5311
Note:
Prior to version 2.0, YSQL was still in beta. As a result, the 2.0 release included a backward-incompatible file format change for YSQL. If you have an existing cluster running releases earlier than 2.0 with YSQL enabled, then you will not be able to upgrade to version 2.0+. Export from your existing cluster and then import into a new cluster (v2.0 or later) to use existing data.
Published by stevebang about 4 years ago
COPY TO
statements by creating a new memory context for the loop over retrieved rows and resetting it after processing each row. #5205
COPY FROM
statement. Reset memory context regularly, per row, when memory is resettable and when rows are read from a file (not stdin
). #5561
COPY FROM
command with OOM fix. Batch sizes can be passed in with ROWS_PER_TRANSACTION
in the COPY OPTION
syntax. #2855 #5453
index_backfill_rpc_timeout_ms
default from 60000
to 30000
and change backfill_index_timeout_grace_margin_ms
default from 50
to 500
. #5494
CREATE OR REPLACE VIEW
. #5071
SPLIT INTO
without a primary key. #4993
UPDATE
statement with the RETURNING
clause. #5366
UPDATE
changes partition so its clear what went wrong, fixed yb_pg_foreign_key
pg_regress
test for semantic merge conflict when updating primary keys and row-level partitioning. #659 #5179 #5310
TABLEGROUP
with the SPLIT
clause. For CREATE TABLE
, usage is blocked in the grammar. For CREATE INDEX
, if NO TABLEGROUP
was provided, then presplitting for the index is allowed; otherwise, an error is issued. #5352
CREATE TABLE
statement. For example, the total number of RPC calls is dropped from 66 to 58 for a simple table like CREATE TABLE t(k INT PRIMARY KEY)
. #5177
ysqlsh
describe metacommands for tablegroups: \dgr[+] [grpname]
to describe tablegroups, \dgrt[+] [grpname]
lists all tables/indexes within the specified tablegroup (or within all tablegroups if grpname
is not specified), and \d <table_name>
is modified to include tablegroup information in the footer, if any. #5088
ALTER TABLEGROUP
statements to support ALTER TABLEGROUP tablegroup_name RENAME TO ...
and ALTER TABLEGROUP tablegroup_name OWNER TO ...
. Also changes pg_tablegroup
entry corresponding to tablegroup_name
to properly reflect new grpname
and grpowner
(if the user has proper permissions or ownership to issue the ALTER TABLEGROUP
statement. #5249
NO TABLEGROUPS
) or select their own tablegroup (TABLEGROUP group_name
). #5293
ysql_dump
, enable serializable-deferrable
mode by default. Add new --no-serializable-deferrable
flag to disable the default mode. #5128
ALTER COLUMN type
for variants that don't require on-disk changes. Specifically only allowing ALTER COLUMN type
for varch(n)
and varbit(n)
. For example, changing column type from varchar(50)
to varchar(255)
. #4424
USING
clause in DELETE
statement and FROM
clause in UPDATE
statement. #738 #5262
EXPLAIN
statement. #2076
initdb
when index backfill is enabled. #5027
skipped
and rows_affected_count
to 0
. #5015
DROP INDEX
statement invalidates table cache entry for the index table but should invalidate the table cache entry for the indexed table. #4974
yb-admin create_database_snapshot
command should not require ysql.
prefix for database name. #4991
pg_statistic
system table lookups and update debugging utilities. #5051
WHERE
clause in CREATE INDEX
statement, return a Not supported
error. #5363
release_version
for system.peers
queries. #5407
TRUNCATE
operations when ycql_require_drop_privs_for_truncate
flag is enabled. When enabled, DROP TABLE
permission is required to truncate a table. Default is false
. #5443
SetPagingState
method in statement_params.cc
. #5441
ycqlsh
should return failure when known that the create (unique) index has failed. #5161
yugabyted
and yb-master fails to start. #5304
server_broadcast_addresses
flag, provide default port if not specified. #2540
0
by resetting timestamp to the maximum value when a peer becomes a leader and when the peer loses leadership. #5502
rpcz/statements
links in yb-tserver
Web UI when pgsql_proxy_bind_address
and cql_proxy_bind_address
are 0.0.0.0
. #4963
DumpReplayStateToStrings
should handle too many WAL entries scenario. Also, log lines only display fields critical for debugging and do not show customer-sensitive information. #5345
BOOTSTRAPPING
/NOT_STARTED
state with its true consensus information instead of marking it as a NON_PARTICIPANT
. #4691
pg_tablegroup
as well as the reltablegroup
column of pg_class
for that relation).MetaCache::TAbleData::stale
is not getting reset back to false
. #5245
op_id
of the last WAL file is less than the committed op_id
. #1560
CREATE TABLEGROUP
and DROP TABLEGROUP
flow. #4525
yb-admin list_snapshots
SHOW_DELETED
flag to show deleted snapshots that are still retained in memory. #5332
yb_client_admin_operation_timeout_sec
for table creation in yb-admin import_snapshot
task. #5295
enable_collect_cdc_metrics
flag and prevent TSAN warnings. #5303
result
of the operation instead of lhs
. #5020
load_balancer_max_concurrent_moves_per_table
and load_balancer_max_concurrent_moves
to improve performance of leader moves. And properly update state for leader stepdowns to prevent check failures. #5021 #5181
load_balancer_max_concurrent_moves
from 10
to 2
. #5461
system.partitions
table requests. #5225
strict_capacity_limit
is set when SetCapacity is called to prevent ASAN failures. #5222
yugabyted
fails to start UI due to class binding failure. #5069
yb-tserver
restart, prioritize bootstrapping transaction status tablets. #4926
yb-admin
commands, clarify syntax for namespace. #5482
SEGV
in Master UI when registering YB-TServer from Raft. #5501
master_ignore_stale_cstate
flag is disabled. #5301
metric_node_name
flag from DEFAULT_NODE_NAME
to hostname:port
. #4859
s3cmd
required for encrypted backup and restore flows. #5593
YB_HOME_DIR
if not set. #5592
AreLeadersOnPreferredOnly
times out when setting preferred zones in Edit Universe. #5406
yb_backup.py
script to remove the sudo
requirement and correctly change the user. #5440
smtpUsername
and smtpPassword
from the payload. #5439
cron
expression must be relative to UTC. Also, add help text indicating when the next scheduled job will run. #4709
yb_backup.py
script and yb-server doesn't have any data directories. #5358
BackupAdmin
role to authorize users to create a backup and restore tasks on universes, but not given other administrative privileges. #4694
yb_backup
script to add "round-robin" behavior to thread allocations to better spread loads across nodes in parallel during snapshot upload or download. #4987
yb_backup.py
script behavior if --keyspace
flag is not specified. #5199
yb_backup.py
script. Explicitly pass the number of threads to concurrently run backup script through UI. The form defaults to the backup script default value of 8 threads if no value is provided. #5283
Cannot read property 'displayName' of undefined
error. #5267
setUniverseKey
should handle errors on a per-customer basis. #3142
Note:
Prior to version 2.0, YSQL was still in beta. As a result, the 2.0 release included a backward-incompatible file format change for YSQL. If you have an existing cluster running releases earlier than 2.0 with YSQL enabled, then you will not be able to upgrade to version 2.0+. Export from your existing cluster and then import it into a new cluster (v2.0 or later) to use existing data.
Published by stevebang about 4 years ago
DROP DATABASE
statement should work with databases deleted on YB-Master. #4710
pg_statistic
system table lookups. #5051
cdc_state
table for xDC metrics if there are no replication streams enabled. #5173
dns_cache_expiration_ms
flag (default is 1 minute). #5201
CatalogManager::ImportSnapshot()
. #5157
cql_processors_limit
flag to control processor allocation. #5057
yugabyted
fails to start UI due to class binding failure. #5069
--webserver_interface
, --rpc_bind_addresses
, and --server_broadcast_addresses
flags. #5002
SCHECK
with LOG(DFATAL)
when checking for restart-safe timestamps in WAL entries. #5314
SCHECK
or RETURN_NOT_OK
. #5182
dns_cache_expiration_ms
flag (default is 1 minute). #5201
system.partitions
table requests. #5225
CHECK
failures if stepdown task is pending on the next run. Sets the global leader balance threshold while allowing progress to be made across tables. Adds new load_balancer_max_concurrent_moves_per_table
flag to limit number of leader moves per table. #5181 and #5021
YBClient
initialization future in TabletPeer
constructor to ensure tablet bootstrap logic can resolve transaction statuses. #5215
0
if not the leader and if the replication is deleted. #5113
fully_*
is populated. #5139
Not the leader
errors should not cause a replica to be marked as failed. #5072
rpc_connections_alive
metrics for YSQL and YCQL APIs. #5223
ssh_user
to air-gap provision script and add to the on-premise template. #5132
--recursive
flag to AZCopy for multi-table restore. #5163
zip_purge_yb_logs.sh
. Fixes issue on Red Hat. #5169
Note:
Prior to version 2.0, YSQL was still in beta. As a result, the 2.0 release included a backward-incompatible file format change for YSQL. If you have an existing cluster running releases earlier than 2.0 with YSQL enabled, then you will not be able to upgrade to version 2.0+. Export from your existing cluster and then import into a new cluster (v2.0 or later) to use existing data.