This is an automated email from the ASF dual-hosted git repository. djwang pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/cloudberry-site.git
commit 3384cbbf4cb894d2d154edcfaf79e13ff7fd281b Author: Dianjin Wang <[email protected]> AuthorDate: Tue Dec 17 19:10:41 2024 +0800 Fix broken anchors warnings in the docs --- docs/functions/index.md | 2 +- docs/functions/json-functions-and-operators.md | 2 +- docs/sql-stmts/copy.md | 2 +- docs/sql-stmts/select.md | 6 +++--- docs/sys-utilities/gpaddmirrors.md | 2 +- docs/sys-utilities/gpexpand.md | 2 +- docs/sys-utilities/gpload.md | 2 +- docs/sys-utilities/psql.md | 2 +- docs/table-storage-models.md | 6 ------ .../current/data-loading/{load-data-overview.md => index.md} | 0 .../current/transactional-concurrency-control.md | 8 +++++--- src/consts/bootcamp.tsx | 2 +- src/pages/bootcamp/102-cbdb-crash-course.md | 2 +- src/pages/bootcamp/cbdb-sandbox.md | 2 +- 14 files changed, 18 insertions(+), 22 deletions(-) diff --git a/docs/functions/index.md b/docs/functions/index.md index 77f68c66a..affb10bfe 100644 --- a/docs/functions/index.md +++ b/docs/functions/index.md @@ -42,7 +42,7 @@ Apache Cloudberry does not support functions that return a table reference (`ran ## Built-in functions and operators -The following table lists the categories of built-in functions and operators supported by PostgreSQL. All functions and operators are supported in Apache Cloudberry as in PostgreSQL with the exception of `STABLE` and `VOLATILE` functions, which are subject to the restrictions noted in [Apache Cloudberry Function Types](#topic27). See the [Functions and Operators](https://www.postgresql.org/docs/14/functions.html) section of the PostgreSQL documentation for more information about these bu [...] +The following table lists the categories of built-in functions and operators supported by PostgreSQL. All functions and operators are supported in Apache Cloudberry as in PostgreSQL with the exception of `STABLE` and `VOLATILE` functions, which are subject to the restrictions noted in [Apache Cloudberry Function Types](#built-in-functions-and-operators). See the [Functions and Operators](https://www.postgresql.org/docs/14/functions.html) section of the PostgreSQL documentation for more i [...] |Operator/Function Category|VOLATILE Functions|STABLE Functions|Restrictions| |--------------------------|------------------|----------------|------------| diff --git a/docs/functions/json-functions-and-operators.md b/docs/functions/json-functions-and-operators.md index 5b266f151..d2f0cae07 100644 --- a/docs/functions/json-functions-and-operators.md +++ b/docs/functions/json-functions-and-operators.md @@ -16,7 +16,7 @@ Apache Cloudberry includes built-in functions and operators that create and mani - [JSON operators](#json-operators) - [JSON creation functions](#json-creation-functions) - [JSON aggregate functions](#json-aggregate-functions) -- [JSON processing functions](#json-processing-functions) +- [JSON processing functions](#sqljson-path-language) ### JSON operators diff --git a/docs/sql-stmts/copy.md b/docs/sql-stmts/copy.md index e868af956..163f8f269 100644 --- a/docs/sql-stmts/copy.md +++ b/docs/sql-stmts/copy.md @@ -204,7 +204,7 @@ Specifies the newline used in your data files — `LF` (Line feed, 0x0A), `CR` ( **`CSV`** -Selects Comma Separated Value (CSV) mode. See [CSV Format](#section9). +Selects Comma Separated Value (CSV) mode. See [CSV Format](#file-formats). **`FILL MISSING FIELDS`** diff --git a/docs/sql-stmts/select.md b/docs/sql-stmts/select.md index 69ccb5e03..11bf9ab7a 100644 --- a/docs/sql-stmts/select.md +++ b/docs/sql-stmts/select.md @@ -371,11 +371,11 @@ If an existing_window_name is specified, it must refer to an earlier entry in th **`PARTITION BY`** -The `PARTITION BY` clause organizes the result set into logical groups based on the unique values of the specified expression. The elements of the `PARTITION BY` clause are interpreted in much the same fashion as elements of a [GROUP BY Clause](#groupbyclause), except that they are always simple expressions and never the name or number of an output column. Another difference is that these expressions can contain aggregate function calls, which are not allowed in a regular `GROUP BY` clau [...] +The `PARTITION BY` clause organizes the result set into logical groups based on the unique values of the specified expression. The elements of the `PARTITION BY` clause are interpreted in much the same fashion as elements of a [GROUP BY Clause](#the-group-by-clause), except that they are always simple expressions and never the name or number of an output column. Another difference is that these expressions can contain aggregate function calls, which are not allowed in a regular `GROUP BY [...] **`ORDER BY`** -Similarly, the elements of the `ORDER BY` list are interpreted in much the same fashion as elements of an [ORDER BY Clause](#orderbyclause), except that the expressions are always taken as simple expressions and never the name or number of an output column. +Similarly, the elements of the `ORDER BY` list are interpreted in much the same fashion as elements of an [ORDER BY Clause](#the-order-by-clause), except that the expressions are always taken as simple expressions and never the name or number of an output column. > **Note** The elements of the `ORDER BY` clause define how to sort the rows > in each partition of the result set. If omitted, rows are returned in > whatever order is most efficient and may vary. @@ -869,7 +869,7 @@ Apache Cloudberry recognizes functional dependency (allowing columns to be omitt **LIMIT and OFFSET** -The clauses `LIMIT` and `OFFSET` are Apache Cloudberry-specific syntax, also used by MySQL. The SQL:2008 standard has introduced the clauses `OFFSET .. FETCH {FIRST|NEXT} ...` for the same functionality, as shown above in [LIMIT Clause](#limitclause). This syntax is also used by IBM DB2. (Applications for Oracle frequently use a workaround involving the automatically generated `rownum` column, which is not available in Apache Cloudberry, to implement the effects of these clauses.) +The clauses `LIMIT` and `OFFSET` are Apache Cloudberry-specific syntax, also used by MySQL. The SQL:2008 standard has introduced the clauses `OFFSET .. FETCH {FIRST|NEXT} ...` for the same functionality, as shown above in [LIMIT Clause](#the-limit-clause). This syntax is also used by IBM DB2. (Applications for Oracle frequently use a workaround involving the automatically generated `rownum` column, which is not available in Apache Cloudberry, to implement the effects of these clauses.) **FOR NO KEY UPDATE, FOR UPDATE, FOR SHARE, and FOR KEY SHARE** diff --git a/docs/sys-utilities/gpaddmirrors.md b/docs/sys-utilities/gpaddmirrors.md index 75bc7ca58..6f3e973bc 100644 --- a/docs/sys-utilities/gpaddmirrors.md +++ b/docs/sys-utilities/gpaddmirrors.md @@ -106,7 +106,7 @@ A configuration file containing one line for each mirror segment you want to cre <contentID>|<address>|<port>|<data_dir> ``` -Where `<contentID>` is the segment instance content ID, `<address>` is the hostname or IP address of the segment host, `<port>` is the communication port, and `<data_dir>` is the segment instance data directory. For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specifying-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#using-host-systems-with-multiple-nics). +Where `<contentID>` is the segment instance content ID, `<address>` is the hostname or IP address of the segment host, `<port>` is the communication port, and `<data_dir>` is the segment instance data directory. For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#use-host-systems-with-multiple-nics). **`-l logfile_directory`** diff --git a/docs/sys-utilities/gpexpand.md b/docs/sys-utilities/gpexpand.md index 4c7d23b5a..e691bde61 100644 --- a/docs/sys-utilities/gpexpand.md +++ b/docs/sys-utilities/gpexpand.md @@ -100,7 +100,7 @@ This file can contain hostnames with or without network interfaces specified. Th > **Note** The Apache Cloudberry segment host naming convention is `sdwN` > where `sdw` is a prefix and `N` is an integer. For example, `sdw1`, `sdw2` > and so on. For hosts with multiple interfaces, the convention is to append a > dash (`-`) and number to the host name. For example, `sdw1-1` and `sdw1-2` > are the two interface names for host `sdw1`. -For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#using-host-systems-with-multiple-nics). +For information about using a hostname or IP address, see [Specifying Hosts using Hostnames or IP Addresses](#specify-hosts-using-hostnames-or-ip-addresses). Also, see [Using Host Systems with Multiple NICs](#use-host-systems-with-multiple-nics). **`-i | --input input_file`** diff --git a/docs/sys-utilities/gpload.md b/docs/sys-utilities/gpload.md index 4bc7780f5..c55964f38 100644 --- a/docs/sys-utilities/gpload.md +++ b/docs/sys-utilities/gpload.md @@ -200,7 +200,7 @@ Required. Begins the load specification section. A `GPLOAD` specification must h Required. Defines the location and the format of the input data to be loaded. `gpload` will start one or more instances of the [gpfdist](/docs/sys-utilities/gpfdist.md) file distribution program on the current host and create the required external table definition(s) in Apache Cloudberry that point to the source data. Note that the host from which you run `gpload` must be accessible over the network by all Apache Cloudberry hosts (coordinator and segments). -SOURCE** +**`SOURCE`** Required. The `SOURCE` block of an `INPUT` specification defines the location of a source file. An `INPUT` section can have more than one `SOURCE` block defined. Each `SOURCE` block defined corresponds to one instance of the [gpfdist](/docs/sys-utilities/gpfdist.md) file distribution program that will be started on the local machine. Each `SOURCE` block defined must have a `FILE` specification. diff --git a/docs/sys-utilities/psql.md b/docs/sys-utilities/psql.md index 99f9b8577..cf6acc784 100644 --- a/docs/sys-utilities/psql.md +++ b/docs/sys-utilities/psql.md @@ -442,7 +442,7 @@ The new query buffer is then re-parsed according to the normal rules of `psql`, If a line number is specified, `psql` will position the cursor on the specified line of the file or query buffer. Note that if a single all-digits argument is given, `psql` assumes it is a line number, not a file name. -See [Environment](#section17) for information about configuring and customizing your editor. +See [Environment](#environment) for information about configuring and customizing your editor. **`\echo text [ ... ]`** diff --git a/docs/table-storage-models.md b/docs/table-storage-models.md index c0906548b..5e9937b89 100644 --- a/docs/table-storage-models.md +++ b/docs/table-storage-models.md @@ -6,12 +6,6 @@ title: Choose the Table Storage Model Apache Cloudberry supports several storage models and a mix of storage models. When you create a table, you choose how to store its data. This document explains the options for table storage and how to choose the best storage model for your workload. -- [Heap Storage](#heap-storage) -- [Append-Optimized Storage](#append-optimized-storage) -- [Choosing Row or Column-Oriented Storage](#choosing-row-or-column-oriented-storage) -- [Altering a Table](#altering-a-table) -- [Dropping a Table](#dropping-a-table) - :::info To simplify the creation of database tables, you can specify the default values for some table storage options with the Apache Cloudberry server configuration parameter `gp_default_storage_options`. ::: diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/data-loading/load-data-overview.md b/i18n/zh/docusaurus-plugin-content-docs/current/data-loading/index.md similarity index 100% rename from i18n/zh/docusaurus-plugin-content-docs/current/data-loading/load-data-overview.md rename to i18n/zh/docusaurus-plugin-content-docs/current/data-loading/index.md diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/transactional-concurrency-control.md b/i18n/zh/docusaurus-plugin-content-docs/current/transactional-concurrency-control.md index c36a65ddd..b49b483ff 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/transactional-concurrency-control.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/transactional-concurrency-control.md @@ -6,9 +6,11 @@ title: 事务中的并发控制 本文档介绍 Apache Cloudberry 中的事务并发控制，包括： -- [多版本并发控制机制](#多版本并发控制机制) -- [锁模式](#锁模式) -- [全局死锁检测器](#全局死锁检测器) +- [事务中的并发控制](#事务中的并发控制) + - [多版本并发控制机制](#多版本并发控制机制) + - [锁模式](#锁模式) + - [全局死锁检测器](#全局死锁检测器) + - [全局死锁检测器对并发 `UPDATE` 和 `DELETE` 操作的管理](#全局死锁检测器对并发-update-和-delete-操作的管理) ## 多版本并发控制机制 diff --git a/src/consts/bootcamp.tsx b/src/consts/bootcamp.tsx index 378070e6d..39502ee21 100644 --- a/src/consts/bootcamp.tsx +++ b/src/consts/bootcamp.tsx @@ -23,7 +23,7 @@ let BOOTCAMP_PAGE_CONFIG = { This part contains a series of tutorials for quickly trying out Cloudberry based on the Cloudberry Sandbox. Before starting to read the tutorials, you are expected to finish installing the - single-node Cloudberry Database by following the{" "} + single-node Apache Cloudberry by following the{" "} <span className="active-color">Cloudberry Sandbox</span>. </> ), diff --git a/src/pages/bootcamp/102-cbdb-crash-course.md b/src/pages/bootcamp/102-cbdb-crash-course.md index e26396148..982feb658 100644 --- a/src/pages/bootcamp/102-cbdb-crash-course.md +++ b/src/pages/bootcamp/102-cbdb-crash-course.md @@ -33,7 +33,7 @@ Topics include: ## Lesson 0. Prerequisite -Before starting this crash course, spend some time going through the [Apache Cloudberry Tutorials Based on Single-Node Installation](./#1-cloudberry-sandbox) to get familiar with Apache Cloudberry and how it works. +Before starting this crash course, spend some time going through the [Apache Cloudberry Tutorials Based on Single-Node Installation](./cbdb-sandbox.md) to get familiar with Apache Cloudberry and how it works. ## Lesson 1. Where to read the official documentation diff --git a/src/pages/bootcamp/cbdb-sandbox.md b/src/pages/bootcamp/cbdb-sandbox.md index 39d353ffa..75937013b 100644 --- a/src/pages/bootcamp/cbdb-sandbox.md +++ b/src/pages/bootcamp/cbdb-sandbox.md @@ -87,5 +87,5 @@ In addition to using the `docker exec` command, you can also use the `ssh` comma ssh gpadmin@localhost # Password: cbdb@123 ``` -Now you have a Apache Cloudberry and can continue with [101 Apache Cloudberry Tutorials](./#2-101-cloudberry-tourials)! Enjoy! +Now you have a Apache Cloudberry and can continue with [101 Apache Cloudberry Tutorials](./102-cbdb-crash-course.md)! Enjoy! --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
