Vitess
v22.0.3Storage & Data2026년 2월 4일
이 릴리스에는 여러 정확성 수정과 Go 도구 체인 의존성 업그레이드가 포함됩니다. 운영자용 기능 추가와 동작 변경도 들어 있습니다. 보안 권고나 명시적으로 설명된 취약점은 없습니다.
그 외 기록된 변경 23건 전체fixes 17 · additions 3 · value changes 3
fixes (17)
- * [release-22.0] Improve Semi-Sync Monitor Behavior to Prevent Errant ERS
- * [release-22.0] evalengine: Fix
NULLdocument handling in JSON functions - * [release-22.0] evalengine: make
JSON_EXTRACTwork with non-static arguments - * [release-22.0] Escape control bytes in JSON strings
- * [release-22.0] Properly Strip Keyspace Table Qualifiers in FK Constraints
- * [release-22.0] Fix cross shard/keyspace joins with derived tables containing a
UNION. - * [release-22.0] Fix column offset tracking for
UNIONs to be case insensitive. - * [release-22.0] Fix
ReloadSchemaincorrectly usingDisableBinlogsvalue ingrpctmclient - * [release-22.0] VDiff: Prevent division by 0 when reconciling mismatches for reference tables
- * [release-22.0] VDiff: Handle the case where a workflow's table has been dropped on the source
- * [release-22.0] VReplication: Properly Handle Sequence Table Initialization For Empty Tables
- * [release-22.0] workflows: avoid accidental deletion to routing rules
- * [release-22.0] connpool: fix connection leak during idle connection reopen
- * [release-22.0] Change connection pool idle expiration logic
- * [release-22.0] binlog_json: fix opaque value parsing to read variable-length
- * [release-22.0]
vtorc: detect errant GTIDs for replicas not connected to primary - * [release-22.0] vschema revert: initialize as nil so that nil checks do not pass later
additions (3)
- * [release-22.0]
vtbench: add--db-credentials-*flags - * [release-22.0] vtorc: add
StaleTopoPrimaryanalysis and recovery - * [release-22.0] Add new
forceflag toDemotePrimaryto force a demotion even when blocked on waiting for semi-sync acks
value changes (3)
- * [release-…] Upgrade the Golang version to
go…×2 - * [release-22.0] vdiff: do not sort by table name in summary, it is not necessary
Vitess 스택에 추가
조치가 필요한 변경이 나오면 주간 메일로 받아볼 수 있습니다. 이번 릴리스처럼 조치가 없는 주에는 메일을 보내지 않습니다.