[FLINK-23156][docs][table] Fix links related to "docs/dev/table/sql/q…

…ueries" (apache#16323)

docs/content.zh/docs/connectors/table/hive/hive_dialect.md

@@ -354,7 +354,7 @@ Hive 方言支持常用的 Hive [DML](https://cwiki.apache.org/confluence/displa
 为了实现更好的语法和语义的兼容，强烈建议使用 [HiveModule]({{< ref "docs/connectors/table/hive/hive_functions" >}}#use-hive-built-in-functions-via-hivemodule) 
 并将其放在 Module 列表的首位，以便在函数解析时优先使用 Hive 内置函数。
 
-Hive 方言不再支持 [Flink SQL 语法]({{< ref "docs/dev/table/sql/queries" >}}) 。 若需使用 Flink 语法，请切换到 `default` 方言。
+Hive 方言不再支持 [Flink SQL 语法]({{< ref "docs/dev/table/sql/queries/overview" >}}) 。 若需使用 Flink 语法，请切换到 `default` 方言。
 
 以下是一个使用 Hive 方言的示例。
 

docs/content.zh/docs/dev/table/concepts/time_attributes.md

@@ -39,7 +39,7 @@ Flink 可以基于几种不同的 *时间* 概念来处理数据。
 时间属性介绍
 -------------------------------
 
-像窗口（在 [Table API]({{< ref "docs/dev/table/tableApi" >}}#group-windows) 和 [SQL]({{< ref "docs/dev/table/sql/queries" >}}#group-windows) ）这种基于时间的操作，需要有时间信息。因此，Table API 中的表就需要提供*逻辑时间属性*来表示时间，以及支持时间相关的操作。
+像窗口（在 [Table API]({{< ref "docs/dev/table/tableApi" >}}#group-windows) 和 [SQL]({{< ref "docs/dev/table/sql/queries/window-agg" >}}) ）这种基于时间的操作，需要有时间信息。因此，Table API 中的表就需要提供*逻辑时间属性*来表示时间，以及支持时间相关的操作。
 
 每种类型的表都可以有时间属性，可以在用CREATE TABLE DDL创建表的时候指定、也可以在 `DataStream` 中指定、也可以在定义 `TableSource` 时指定。一旦时间属性定义好，它就可以像普通列一样使用，也可以在时间相关的操作中使用。
 

docs/content.zh/docs/dev/table/concepts/versioned_tables.md

@@ -181,7 +181,7 @@ currency_time currency  rate
 11:49:00      Pounds    108
 ```
 
-为了在 `RatesHistory` 上定义版本表，Flink 支持通过[去重查询]({{< ref "docs/dev/table/sql/queries" >}}#去重)定义版本视图，
+为了在 `RatesHistory` 上定义版本表，Flink 支持通过[去重查询]({{< ref "docs/dev/table/sql/queries/deduplication" >}}#去重)定义版本视图，
 去重查询可以产出一个有序的 changelog 流，去重查询能够推断主键并保留原始数据流的事件时间属性。
 
 ```sql
@@ -361,6 +361,6 @@ tEnv.registerFunction("Rates", rates)                                          /
 行`(1)`创建了一个 `rates` [时态表函数](#时态表函数)，
 这使我们可以在[ Table API ]({{< ref "docs/dev/table/tableApi" >}}#joins)中使用 `rates` 函数。
 
-行`(2)`在表环境中注册名称为 `Rates` 的函数，这使我们可以在[ SQL ]({{< ref "docs/dev/table/sql/queries" >}}#joins)中使用 `Rates` 函数。
+行`(2)`在表环境中注册名称为 `Rates` 的函数，这使我们可以在[ SQL ]({{< ref "docs/dev/table/sql/queries/joins" >}})中使用 `Rates` 函数。
 
 {{< top >}}

docs/content.zh/docs/dev/table/sql/explain.md

@@ -184,5 +184,5 @@ Union(all=[true], union all=[count, word])
 EXPLAIN PLAN FOR <query_statement_or_insert_statement>
 ```
 
-For query syntax, please refer to [Queries]({{< ref "docs/dev/table/sql/queries" >}}#supported-syntax) page.
+For query syntax, please refer to [Queries]({{< ref "docs/dev/table/sql/queries/overview" >}}) page.
 For INSERT, please refer to [INSERT]({{< ref "docs/dev/table/sql/insert" >}}) page.

docs/content.zh/docs/dev/table/sql/overview.md

@@ -30,7 +30,7 @@ under the License.
 
 本页面列出了目前 Flink SQL 所支持的所有语句：
 
-- [SELECT (Queries)]({{< ref "docs/dev/table/sql/queries" >}})
+- [SELECT (Queries)]({{< ref "docs/dev/table/sql/queries/overview" >}})
 - [CREATE TABLE, DATABASE, VIEW, FUNCTION]({{< ref "docs/dev/table/sql/create" >}})
 - [DROP TABLE, DATABASE, VIEW, FUNCTION]({{< ref "docs/dev/table/sql/drop" >}})
 - [ALTER TABLE, DATABASE, FUNCTION]({{< ref "docs/dev/table/sql/alter" >}})

docs/content/docs/connectors/table/hive/hive_dialect.md

@@ -364,7 +364,7 @@ HiveQL supported by the Hive dialect.
 In order to have better syntax and semantic compatibility, it's highly recommended to use [HiveModule]({{< ref "docs/connectors/table/hive/hive_functions" >}}#use-hive-built-in-functions-via-hivemodule)
 and place it first in the module list, so that Hive built-in functions can be picked up during function resolution.
 
-Hive dialect no longer supports [Flink SQL queries]({{< ref "docs/dev/table/sql/queries" >}}). Please switch to `default`
+Hive dialect no longer supports [Flink SQL queries]({{< ref "docs/dev/table/sql/queries/overview" >}}). Please switch to `default`
 dialect if you'd like to write in Flink syntax.
 
 Following is an example of using hive dialect to run some queries.

docs/content/docs/dev/table/concepts/dynamic_tables.md

@@ -118,7 +118,7 @@ The first query is a simple `GROUP-BY COUNT` aggregation query. It groups the `c
 
 When the query starts, the `clicks` table (left-hand side) is empty. The query computes the result table when the first row is inserted. After the first row `[Mary, ./home]` arrives, the result table (right-hand side, top) consists of a single row `[Mary, 1]`. When the second row `[Bob, ./cart]` is inserted into the `clicks` table, the query updates the result table and inserts a new row `[Bob, 1]`. The third row, `[Mary, ./prod?id=1]` yields an update of an already computed result row such that `[Mary, 1]` is updated to `[Mary, 2]`. Finally, the query inserts a third row `[Liz, 1]` into the result table, when the fourth row is appended to the `clicks` table.
 
-The second query is similar to the first one but groups the `clicks` table in addition to the `user` attribute also on an [hourly tumbling window]({{< ref "docs/dev/table/sql/queries" >}}#group-windows) before it counts the number of URLs (time-based computations such as windows are based on special [time attributes](time_attributes.html) are discussed later). Again, the figure shows the input and output at different points in time to visualize the changing nature of dynamic tables.
+The second query is similar to the first one but groups the `clicks` table in addition to the `user` attribute also on an [hourly tumbling window]({{< ref "docs/dev/table/sql/queries/window-agg" >}}#group-window-functions) before it counts the number of URLs (time-based computations such as windows are based on special [time attributes](time_attributes.html) are discussed later). Again, the figure shows the input and output at different points in time to visualize the changing nature of dynamic tables.
 
 {{< img alt="Continuous Group-Window Query" src="/fig/table-streaming/query-groupBy-window-cnt.png" width="80%" >}}
 

docs/content/docs/dev/table/concepts/versioned_tables.md

@@ -130,7 +130,7 @@ The `JSON` format does not support native changelog semantics, so Flink can only
 
 Flink interprets each row as an `INSERT` to the table, meaning we cannot define a `PRIMARY KEY` over currency.
 However, it is clear to us (the query developer) that this table has all the necessary information to define a versioned table. 
-Flink can reinterpret this table as a versioned table by defining a [deduplication query]({{< ref "docs/dev/table/sql/queries" >}}#deduplication)
+Flink can reinterpret this table as a versioned table by defining a [deduplication query]({{< ref "docs/dev/table/sql/queries/deduplication" >}}#deduplication)
 which produces an ordered changelog stream with an inferred primary key (currency) and event time (update_time). 
 
 ```sql

docs/content/docs/dev/table/sql/explain.md

@@ -185,5 +185,5 @@ Union(all=[true], union all=[count, word])
 EXPLAIN PLAN FOR <query_statement_or_insert_statement>
 ```
 
-For query syntax, please refer to [Queries]({{< ref "docs/dev/table/sql/queries" >}}#supported-syntax) page.
+For query syntax, please refer to [Queries]({{< ref "docs/dev/table/sql/queries/overview" >}}) page.
 For INSERT, please refer to [INSERT]({{< ref "docs/dev/table/sql/insert" >}}) page.

docs/content/docs/dev/table/sql/overview.md

@@ -30,7 +30,7 @@ This page describes the SQL language supported in Flink, including Data Definiti
 
 This page lists all the supported statements supported in Flink SQL for now:
 
-- [SELECT (Queries)]({{< ref "docs/dev/table/sql/queries" >}})
+- [SELECT (Queries)]({{< ref "docs/dev/table/sql/queries/overview" >}})
 - [CREATE TABLE, DATABASE, VIEW, FUNCTION]({{< ref "docs/dev/table/sql/create" >}})
 - [DROP TABLE, DATABASE, VIEW, FUNCTION]({{< ref "docs/dev/table/sql/drop" >}})
 - [ALTER TABLE, DATABASE, FUNCTION]({{< ref "docs/dev/table/sql/alter" >}})