[DOC-306] [DOC-320] [DOC-357] [yba] 2024.1 Release management enhancement, 2024.1 version naming changes.

bin/yugabyted

@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
 from __future__ import unicode_literals
 
 import argparse
@@ -10,7 +10,6 @@ import os
 import re
 import resource
 import shutil
-from distutils.spawn import find_executable
 import subprocess
 import sys
 import time
@@ -345,10 +344,11 @@ METRICS_SNAPSHOT_LIST = [
     "handler_latency_yb_tserver_TabletServerService_Write_sum",
     "disk_usage", "cpu_usage", "node_up"
 ]
+PG_PARITY_FLAGS_LIST = [
+    "yb_enable_read_committed_isolation=true",
+    "ysql_enable_read_request_caching=true"
+]
 PG_PARITY_FLAGS_DICT = {
-"allowed_preview_flags_csv": "yb_enable_read_committed_isolation=true,"
-                             "ysql_enable_read_request_caching=true",
-
 "ysql_pg_conf_csv": "yb_enable_base_scans_cost_model=true,"
                       "yb_enable_optimizer_statistics=true,"
                       "yb_bnl_batch_size=1024,"
@@ -2002,8 +2002,8 @@ class ControlScript(object):
             prereqs_warn.add('transparent_hugepages')
             prereqs_warn_flag = True
 
-        ntp_check = find_executable('ntpd')
-        chrony_check = find_executable('chronyd')
+        ntp_check = shutil.which('ntpd')
+        chrony_check = shutil.which('chronyd')
         if not ntp_check and not chrony_check:
             prereqs_warn.add('ntp/chrony')
             prereqs_warn_flag = True
@@ -2823,6 +2823,26 @@ class ControlScript(object):
 
         master_flags = self.configs.saved_data.get("master_flags","")
 
+        if self.configs.temp_data.get("enable_pg_parity"):
+            # Process simple flags from PG_PARITY_FLAGS_LIST
+            existing_flags = {}
+            current_flags = master_flags.split(',')
+            for flag in current_flags:
+                if '=' in flag:
+                    key, value = flag.split('=', 1)
+                    existing_flags[key] = value
+
+            for flag in PG_PARITY_FLAGS_LIST:
+                key = flag.split('=')[0]
+                if existing_flags.get(key) is None:
+                    if master_flags and not master_flags.endswith(","):
+                        master_flags += ","
+                    # Add the missing flag to the master flags
+                    master_flags += flag
+
+            # Update the master_flags in self.configs.saved_data with pg_parity flags
+            self.configs.saved_data["master_flags"] = master_flags
+
         # if a join ip is specified, bring up a shell mode master
         if not join_ip:
             yb_master_cmd.append("--master_addresses={}".format(master_addresses))
@@ -2905,6 +2925,23 @@ class ControlScript(object):
         tserver_flags = self.configs.saved_data.get("tserver_flags","")
 
         if self.configs.temp_data.get("enable_pg_parity"):
+            # Process simple flags from PG_PARITY_FLAGS_LIST
+            existing_flags = {}
+            current_flags = tserver_flags.split(',')
+            for flag in current_flags:
+                if '=' in flag:
+                    key, value = flag.split('=', 1)
+                    existing_flags[key] = value
+
+            for flag in PG_PARITY_FLAGS_LIST:
+                key = flag.split('=')[0]
+                if existing_flags.get(key) is None:
+                    if tserver_flags and not tserver_flags.endswith(","):
+                        tserver_flags += ","
+                    # Add the missing flag to the tserver flags
+                    tserver_flags += flag
+
+            # Process CSV flags from PG_PARITY_FLAGS_DICT
             for pg_parity_flag, pg_parity_flag_values in PG_PARITY_FLAGS_DICT.items():
                 # If pg_parity_flag present in tserver_flags
                 # Extract the value and append any default missing pg_parity_flag_values

build-support/common-test-env.sh

@@ -1876,6 +1876,7 @@ run_python_doctest() {
     if [[ $python_file == managed/* ||
           $python_file == cloud/* ||
           $python_file == src/postgres/src/test/locale/sort-test.py ||
+          $python_file == src/postgres/third-party-extensions/postgresql_anonymizer/* ||
           $python_file == bin/test_bsopt.py ||
           $python_file == thirdparty/* ]]; then
       continue

docs/content/preview/admin/yb-admin.md

@@ -380,7 +380,7 @@ Returns tables in the following format, depending on the flags used:
 <db_type>.<namespace>.<table_name> table_id table_type
 ```
 
-* *db_type*: The type of database. Valid values include `ysql`, `ycql`, `yedis`, and `unknown`.
+* *db_type*: The type of database. Valid values include `ysql`, `ycql`, and `unknown`.
 * *namespace*: The name of the database (for YSQL) or keyspace (for YCQL).
 * *table_name*: The name of the table.
 * *table_type*: The type of table. Valid values include `catalog`, `table`, `index`, and `other`.
@@ -863,7 +863,7 @@ yb-admin \
 ```
 
 * *master-addresses*: Comma-separated list of YB-Master hosts and ports. Default value is `localhost:7100`.
-* *keyspace*: The name of the database or keyspace formatted as <ycql|ysql|yedis>.<keyspace>.
+* *keyspace*: The name of the database or keyspace formatted as <ycql|ysql>.<keyspace>.
 * *table_name*: The name of the table name.
 * *table_id*: The unique UUID associated with the table.
 * *flush_timeout_in_seconds*: Specifies duration (in seconds) before flushing snapshot. Default value is `60`. To skip flushing, set the value to `0`.

docs/content/preview/admin/yb-ctl.md

@@ -117,12 +117,6 @@ Restarts the specified node in a running cluster. It also takes an optional flag
 
 For details and examples, see [Restart node with placement information](#restart-node-with-placement-information).
 
-##### setup_redis
-
-Enables YugabyteDB support for the Redis-compatible YEDIS API.
-
-For details and examples, see [Initialize the YEDIS API](#initialize-the-yedis-api).
-
 ## Flags
 
 ##### --help, -h
@@ -157,7 +151,7 @@ For details and examples, see [Create a local cluster with custom flags](#create
 
 **Example**
 
-To enable [YSQL authentication](../../secure/enable-authentication/ysql/), you can use the `--tserver_flags` flag to add the `yb-tserver` [`--ysql_enable_auth`](../yb-tserver/#ysql-enable-auth) flag to the `yb-ctl create | start | restart` commands.
+To enable [YSQL authentication](../../secure/enable-authentication/authentication-ysql/), you can use the `--tserver_flags` flag to add the `yb-tserver` [`--ysql_enable_auth`](../yb-tserver/#ysql-enable-auth) flag to the `yb-ctl create | start | restart` commands.
 
 ```sh
 $./bin/yb-ctl create --tserver_flags "ysql_enable_auth=true"
@@ -310,7 +304,6 @@ Following is the output shown for a 3-node RF3 cluster.
 | JDBC                : jdbc:postgresql://127.0.0.1:5433/yugabyte                                  |
 | YSQL Shell          : bin/ysqlsh                                                                 |
 | YCQL Shell          : bin/ycqlsh                                                                 |
-| YEDIS Shell         : bin/redis-cli                                                              |
 | Web UI              : http://127.0.0.1:7000/                                                     |
 | Cluster Data        : /Users/testuser12/yugabyte-data                                            |
 ----------------------------------------------------------------------------------------------------
@@ -320,7 +313,6 @@ Following is the output shown for a 3-node RF3 cluster.
 | JDBC                : jdbc:postgresql://127.0.0.1:5433/yugabyte                                  |
 | YSQL Shell          : bin/ysqlsh                                                                 |
 | YCQL Shell          : bin/ycqlsh                                                                 |
-| YEDIS Shell         : bin/redis-cli                                                              |
 | data-dir[0]         : /Users/testuser12/yugabyte-data/node-1/disk-1/yb-data                      |
 | yb-tserver Logs     : /Users/testuser12/yugabyte-data/node-1/disk-1/yb-data/tserver/logs         |
 | yb-master Logs      : /Users/testuser12/yugabyte-data/node-1/disk-1/yb-data/master/logs          |
@@ -331,7 +323,6 @@ Following is the output shown for a 3-node RF3 cluster.
 | JDBC                : jdbc:postgresql://127.0.0.2:5433/yugabyte                                  |
 | YSQL Shell          : bin/ysqlsh -h 127.0.0.2                                                    |
 | YCQL Shell          : bin/ycqlsh 127.0.0.2                                                       |
-| YEDIS Shell         : bin/redis-cli -h 127.0.0.2                                                 |
 | data-dir[0]         : /Users/testuser12/yugabyte-data/node-2/disk-1/yb-data                      |
 | yb-tserver Logs     : /Users/testuser12/yugabyte-data/node-2/disk-1/yb-data/tserver/logs         |
 | yb-master Logs      : /Users/testuser12/yugabyte-data/node-2/disk-1/yb-data/master/logs          |
@@ -342,7 +333,6 @@ Following is the output shown for a 3-node RF3 cluster.
 | JDBC                : jdbc:postgresql://127.0.0.3:5433/yugabyte                                  |
 | YSQL Shell          : bin/ysqlsh -h 127.0.0.3                                                    |
 | YCQL Shell          : bin/ycqlsh 127.0.0.3                                                       |
-| YEDIS Shell         : bin/redis-cli -h 127.0.0.3                                                 |
 | data-dir[0]         : /Users/testuser12/yugabyte-data/node-3/disk-1/yb-data                      |
 | yb-tserver Logs     : /Users/testuser12/yugabyte-data/node-3/disk-1/yb-data/tserver/logs         |
 | yb-master Logs      : /Users/testuser12/yugabyte-data/node-3/disk-1/yb-data/master/logs          |
@@ -574,11 +564,3 @@ $ ./bin/yb-ctl wipe_restart --placement_info "cloud1.region1.zone1"
 ```sh
 $ ./bin/yb-ctl wipe_restart --master_flags "log_cache_size_limit_mb=128,log_min_seconds_to_retain=20,master_backup_svc_queue_length=70" --tserver_flags "log_inject_latency=false,log_segment_size_mb=128,raft_heartbeat_interval_ms=1000"
 ```
-
-### Initialize the YEDIS API
-
-The `setup_redis` command to initialize YugabyteDB's Redis-compatible YEDIS API.
-
-```sh
-$ ./bin/yb-ctl setup_redis
-```

docs/content/preview/admin/yb-ts-cli.md

@@ -130,7 +130,7 @@ yb-ts-cli  [ --server_address=<host>:<port> ] count_intents
 
 ##### current_hybrid_time
 
-Prints the value of the current [hybrid time](../../architecture/transactions/transactions-overview/#mvcc-using-hybrid-time).
+Prints the value of the current [hybrid time](../../architecture/transactions/transactions-overview/#hybrid-logical-clocks).
 
 **Syntax**
 

docs/content/preview/api/ysql/exprs/func_nextval.md

@@ -26,7 +26,7 @@ Specify the name of the sequence.
 
 ## Caching values on the YB-TServer
 
-If [ysql_sequence_cache_method](../../../../reference/configuration/yb-tserver/#ysql-sequence-cache-method) is set to `server`, sequence values are cached on the YB-TServer, to be shared with all connections on that YB-TServer. This is beneficial when many connections on the server are expected to get the next value of a sequence. Normally, each connection waits for replication to complete, which can be expensive, especially in a multi-region cluster. With the server cache method, only one connection waits for RAFT replication and the rest retrieve values from the same cached range.
+If [ysql_sequence_cache_method](../../../../reference/configuration/yb-tserver/#ysql-sequence-cache-method) is set to `server`, sequence values are cached on the YB-TServer, to be shared with all connections on that YB-TServer. This is beneficial when many connections on the server are expected to get the next value of a sequence. Normally, each connection waits for replication to complete, which can be expensive, especially in a multi-region cluster. With the server cache method, only one connection waits for Raft replication and the rest retrieve values from the same cached range.
 
 When the server cache method is used, the connection cache size is implicitly set to 1. When the cache method is changed from `connection` to `server`, sequences continue to use the connection cache until it is exhausted, at which point they begin using the server cache. When the cache method is changed from `server` to `connection`, sequences immediately begin using a connection cache. The server cache is not cleared in this case, and its values can later be retrieved if the cache method is again set to `server`.
 

docs/content/preview/api/ysql/exprs/geo_partitioning_helper_functions/func_yb_is_local_table.md

@@ -69,7 +69,7 @@ This function is primarily helpful while implementing [Row-level geo-partitionin
     CREATE TABLESPACE us_east2_tablespace WITH (replica_placement=' {"num_replicas":1,"placement_blocks":[     {"cloud":"aws","region":"us-east-2","zone":"us-east-2c","min_num_replicas":1}]}');
     ```
 
-     For more information on how to set up a cluster with [yugabyted](../../../../../reference/configuration/yugabyted/) or [YugabyteDB Anywhere](https://www.yugabyte.com/anywhere/) with corresponding tablespaces, see [tablespaces](../../../../../explore/ysql-language-features/going-beyond-sql/tablespaces).
+     For more information on how to set up a cluster with [yugabyted](../../../../../reference/configuration/yugabyted/) or [YugabyteDB Anywhere](https://www.yugabyte.com/anywhere/) with corresponding tablespaces, see [tablespaces](../../../../../explore/going-beyond-sql/tablespaces/).
 
 1. Using the tablespaces, you can create a geo-partitioned table as follows. This is a partitioned table with 3 partitions, where each partition is pinned to a different location.
 

docs/content/preview/api/ysql/exprs/geo_partitioning_helper_functions/func_yb_server_region.md

@@ -77,7 +77,7 @@ Do the following to create a 3-node multi-region cluster and a geo-partitioned t
     CREATE TABLESPACE us_east2_tablespace WITH (replica_placement=' {"num_replicas":1,"placement_blocks":[{"cloud":"aws","region":"us-east-2","zone":"us-east-2c","min_num_replicas":1}]}');
     ```
 
-    For more information on how to set up a cluster with [yugabyted](../../../../../reference/configuration/yugabyted/) or [YugabyteDB Anywhere](https://www.yugabyte.com/anywhere/) with corresponding tablespaces, see [tablespaces](../../../../../explore/ysql-language-features/going-beyond-sql/tablespaces).
+    For more information on how to set up a cluster with [yugabyted](../../../../../reference/configuration/yugabyted/) or [YugabyteDB Anywhere](https://www.yugabyte.com/anywhere/) with corresponding tablespaces, see [tablespaces](../../../../../explore/going-beyond-sql/tablespaces/).
 
 1. Using the tablespaces, you can create a geo-partitioned table as follows. This is a partitioned table with 3 partitions, where each partition is pinned to a different location based on the regions. The geo_partition column value is default to be the currently connected region as in `yb_server_region()`.
 

docs/content/preview/api/ysql/the-sql-language/statements/ddl_create_index.md

@@ -85,7 +85,7 @@ Specify a list of columns which will be included in the index as non-key columns
 
 ### TABLESPACE clause
 
-Specify the name of the [tablespace](../../../../../explore/ysql-language-features/going-beyond-sql/tablespaces/) that describes the placement configuration for this index. By default, indexes are placed in the `pg_default` tablespace, which spreads the tablets of the index evenly across the cluster.
+Specify the name of the [tablespace](../../../../../explore/going-beyond-sql/tablespaces/) that describes the placement configuration for this index. By default, indexes are placed in the `pg_default` tablespace, which spreads the tablets of the index evenly across the cluster.
 
 ### WHERE clause
 
@@ -246,7 +246,7 @@ CREATE UNIQUE INDEX users_email_idx ON users(lower(email));
 
 Creating a unique index prevents inserting duplicate email addresses using a different case.
 
-Note that index expressions are only evaluated at index time, so to use the index for a specific query the expression must match exactly. 
+Note that index expressions are only evaluated at index time, so to use the index for a specific query the expression must match exactly.
 
 ```plpgsql
 SELECT * FROM users WHERE lower(email)='user@example.com'; # will use the index created above

docs/content/preview/api/ysql/the-sql-language/statements/ddl_create_table.md

@@ -53,7 +53,7 @@ If the primary key specification is `PRIMARY KEY(a, b)`, then column `a` is used
 
 {{<note title="Tables always have a primary key">}}
 
-PostgreSQL's table storage is heap-oriented—so a table with no primary key is viable. However YugabyteDB's table storage is index-oriented (see [DocDB Persistence](../../../../../architecture/docdb/persistence/)), so a table isn't viable without a primary key.
+PostgreSQL's table storage is heap-oriented—so a table with no primary key is viable. However YugabyteDB's table storage is index-oriented (see [DocDB Persistence](../../../../../architecture/docdb)), so a table isn't viable without a primary key.
 
 Therefore, if you don't specify a primary key at table-creation time, YugabyteDB will use the internal `ybrowid` column as `PRIMARY KEY` and the table will be sharded on `ybrowid HASH`.
 
@@ -89,29 +89,29 @@ Constraints marked as `INITIALLY DEFERRED` will be checked at the end of the tra
 
 ### IDENTITY columns
 
-Create the column as an identity column. 
+Create the column as an identity column.
 
 An implicit sequence will be created, attached to it, and new rows will automatically have values assigned from the sequence. IDENTITY columns are implicitly `NOT NULL`.
 
 `ALWAYS` and `BY DEFAULT` will determine how user-provided values are handled in `INSERT` and `UPDATE` statements.
 
 On an `INSERT` statement:
-- when `ALWAYS` is used, a user-provided value is only accepted if the `INSERT` statement uses `OVERRIDING SYSTEM VALUE`. 
+- when `ALWAYS` is used, a user-provided value is only accepted if the `INSERT` statement uses `OVERRIDING SYSTEM VALUE`.
 - when `BY DEFAULT` is used, then the user-provided value takes precedence. See [INSERT statement](../dml_insert/) for reference. (In the `COPY` statement, user-supplied values are always used regardless of this setting.)
 
 On an `UPDATE` statement:
 - when `ALWAYS` is used, a column update to a value other than `DEFAULT` will be rejected.
 - when `BY DEFAULT` is used, the column can be updated normally. (`OVERRIDING` clause cannot be used for the UPDATE statement)
 
-The `sequence_options` optional clause can be used to override the options of the generated sequence. 
+The `sequence_options` optional clause can be used to override the options of the generated sequence.
 
 See [CREATE SEQUENCE](../ddl_create_sequence) for reference.
 
 #### Multiple Identity Columns
 
-PostgreSQL and YugabyteDB allow a table to have more than one identity column. The SQL standard specifies that a table can have at most one identity column. 
+PostgreSQL and YugabyteDB allow a table to have more than one identity column. The SQL standard specifies that a table can have at most one identity column.
 
-This relaxation primarily aims to provide increased flexibility for carrying out schema modifications or migrations. 
+This relaxation primarily aims to provide increased flexibility for carrying out schema modifications or migrations.
 
 Note that the [INSERT](../dml_insert/) command can only accommodate one override clause for an entire statement. As a result, having several identity columns, each exhibiting distinct behaviours, is not effectively supported.
 
@@ -122,7 +122,7 @@ Using this qualifier will create a temporary table. Temporary tables are visible
 
 ### TABLESPACE
 
-Specify the name of the [tablespace](../../../../../explore/ysql-language-features/going-beyond-sql/tablespaces/) that describes the placement configuration for this table. By default, tables are placed in the `pg_default` tablespace, which spreads the tablets of the table evenly across the cluster.
+Specify the name of the [tablespace](../../../../../explore/going-beyond-sql/tablespaces/) that describes the placement configuration for this table. By default, tables are placed in the `pg_default` tablespace, which spreads the tablets of the table evenly across the cluster.
 
 ### SPLIT INTO
 

docs/content/preview/api/ysql/the-sql-language/statements/ddl_create_tablespace.md

@@ -32,7 +32,7 @@ Use the `CREATE TABLESPACE` statement to create a tablespace in the cluster. It
 
 ## Examples
 
-See [Tablespaces](../../../../../explore/ysql-language-features/going-beyond-sql/tablespaces/) and [Row Level Geo Partitioning](../../../../../explore/multi-region-deployments/row-level-geo-partitioning/) for full guides.
+See [Tablespaces](../../../../../explore/going-beyond-sql/tablespaces/) and [Row Level Geo Partitioning](../../../../../explore/multi-region-deployments/row-level-geo-partitioning/) for full guides.
 
 ## See also