v2.0.1 release notes
Docker
- [YSQL] Allow ALTER COLUMN add/set/drop identity.
- [YSQL] PostgreSQL error code handling to avoid string-based error comparisons.#1289
- [YSQL] Fix duplicate key error being suppressed in COPY.
- [YSQL] VERIFY_RESULT creates undesirable copy of Result’s value.#2298
- [YSQL] Warn on non-txn COPY with incompatible relation.
- [YSQL] PostgreSQL error code handling to avoid string-based error comparisons.#1289
- [YSQL] Aggregate pushdowns in YSQL.
- [YSQL] Use keyspace id instead of name in requests from yb-admin to catalog_manager.#1476
- [YSQL] Fix insert into temp table in function body assertion error.
- [YSQL] Fix memory leak in psql. #2388
- [YSQL] Add default password for yugabyte user.
- [YCQL] Fixed permission check for DROP TYPE.#2373
- [YCQL] Fix for ‘value too long’ error code mapping.
- [YCQL] ‘expression not yet supported’ error for old-format index update.#2470
- Do not retry flush/compact async tasks.
- Make yb-admin log an error message instead of fatal-ing on failed init.#2141
- Propagate timeout to transaction.
- Warn on non-txn COPY with incompatible relation.#2278
- [2DC] Add Exponential Backoff to CDC Consumer.
- Add support for cotable id in EnumerateIntents (needed for transactional DDL).#1404
- TServer blacklisting for leadership role.
- [2DC] Reduce checkpoint frequency, avoid self looping in CDC producer, apply polling delaycorrectly. #2364
- Request intents cleanup even on failed replicas.
- Add number of sst files to tables and tablets pages for tserver.#2230
- Fix role and term cache.
- yb-admin add RF to add_read_replicas. #2395
- [2DC] Fix transaction status and record handling in CDC producer/consumer.
- Handle concurrent shutdown and remote bootstrap.#2428
- [CDC] Fix bug in condition check for tablet leader.
- Fix remote bootstrap for encryption at rest.#2462
- Implement dynamic priorities for compaction tasks.
- [2DC] Update checkpoint for replicated records, ignore tablet status while looking up peer.#2487
- [2DC] yb-admin command to pause/resume replication.
- If you don’t care about preserving your existing data, then delete your cluster, and create a newcluster with 2.0.x.x
- If you want to continue using your existing data, then please save your data,delete the cluster, create a new cluster with 2.0.x.x and then load the previously saved data.