Skip to content

Update manual version references to 2.0.10 #1179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
HTHou merged 1 commit into from
Jul 9, 2026
Merged

Update manual version references to 2.0.10 #1179

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions src/UserGuide/Master/Table/AI-capability/AINode_Upgrade_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,7 @@ It costs 1.615s
2. The model must inherit an AINode inference pipeline class (currently supports forecasting pipeline):
* iotdb-core/ainode/iotdb/ainode/core/inference/pipeline/basic_pipeline.py

**Before V2.0.9-beta**
**Before V2.0.10**
```Python
class BasicPipeline(ABC):
def __init__(self, model_id, **model_kwargs):
Expand Down Expand Up @@ -247,7 +247,7 @@ It costs 1.615s
pass
```

**From V2.0.9-beta onwards**
**From V2.0.10 onwards**
```Python
class BasicPipeline(ABC):
def __init__(self, model_id, **model_kwargs):
Expand Down Expand Up @@ -335,7 +335,7 @@ It costs 1.615s

3. Modify the model configuration file `config.json` to ensure it contains the following fields:

**Before V2.0.9-beta**
**Before V2.0.10**
```JSON
{
"auto_map": {
Expand All @@ -350,7 +350,7 @@ It costs 1.615s
* The inference pipeline class **must** be inherited and specified;
* For built-in and user-defined models managed by AINode, `model_type` also serves as a unique non-duplicable identifier. That is, the model type to be registered must not duplicate any existing model types; models created via fine-tuning will inherit the model type of the original model.

**From V2.0.9-beta onwards**
**From V2.0.10 onwards**
> The `model_type` parameter is **not required**
```JSON
{
Expand Down
2 changes: 1 addition & 1 deletion src/UserGuide/Master/Table/Reference/System-Tables_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -714,7 +714,7 @@ IoTDB> SELECT * FROM information_schema.services
```

### 2.22 TABLE_DISK_USAGE
> This system table is available since version V2.0.9-beta
> This system table is available since version V2.0.10

Used to display the disk space usage of specified tables (excluding views), including the size of ChunkGroups and the size of Metadata.

Expand Down
6 changes: 3 additions & 3 deletions src/UserGuide/Master/Table/SQL-Manual/Basis-Function_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -162,7 +162,7 @@ SELECT LEAST(temperature,humidity) FROM table2;
| COUNT_IF | COUNT_IF(exp) counts the number of rows that satisfy a specified boolean expression. | `exp` must be a boolean expression,(e.g. `count_if(temperature>20)`) | INT64 |
| APPROX_COUNT_DISTINCT | The APPROX_COUNT_DISTINCT(x[, maxStandardError]) function provides an approximation of COUNT(DISTINCT x), returning the estimated number of distinct input values. | `x`: The target column to be calculated, supports all data types.<br>`maxStandardError` (optional): Specifies the maximum standard error allowed for the function's result. Valid range is [0.0040625, 0.26]. Defaults to 0.023 if not specified. | INT64 |
| APPROX_MOST_FREQUENT | The APPROX_MOST_FREQUENT(x, k, capacity) function is used to approximately calculate the top k most frequent elements in a dataset. It returns a JSON-formatted string where the keys are the element values and the values are their corresponding approximate frequencies. （Available since V2.0.5.1) | `x` : The column to be calculated, supporting all existing data types in IoTDB;<br> `k`: The number of top-k most frequent values to return;<br>`capacity`: The number of buckets used for computation, which relates to memory usage—a larger value reduces error but consumes more memory, while a smaller value increases error but uses less memory. | STRING |
| APPROX_PERCENTILE | The APPROX_PERCENTILE function calculates the value at a specified percentile in a dataset, helping quickly understand data distribution (e.g., median, quartiles). It supports weighted percentile calculation. If the percentile does not point to an exact position, it returns a linear interpolation of adjacent values at that position.Memory usage depends on the number of centroids, and the maximum number of centroids can be limited using the compression parameter. Error can be estimated using empirical formulas.Note: This function is supported since V2.0.9-beta. | Unweighted Version: APPROX_PERCENTILE(x, percentage) <br> x: Column to compute. Supports all numeric types: INT32, INT64, FLOAT, DOUBLE, TIMESTAMP. <br> percentage: Target percentile, DOUBLE type. <br>Weighted Version: APPROX_PERCENTILE(x, w, percentage)<br>x: Column to compute. Supports all numeric types: INT32, INT64, FLOAT, DOUBLE, TIMESTAMP.<br>w: Weight column, integer type (must align with the length of x; NULL or 0 means the row is ignored).<br>percentage: Target percentile, DOUBLE type. | Same as the input column x. |
| APPROX_PERCENTILE | The APPROX_PERCENTILE function calculates the value at a specified percentile in a dataset, helping quickly understand data distribution (e.g., median, quartiles). It supports weighted percentile calculation. If the percentile does not point to an exact position, it returns a linear interpolation of adjacent values at that position.Memory usage depends on the number of centroids, and the maximum number of centroids can be limited using the compression parameter. Error can be estimated using empirical formulas.Note: This function is supported since V2.0.10. | Unweighted Version: APPROX_PERCENTILE(x, percentage) <br> x: Column to compute. Supports all numeric types: INT32, INT64, FLOAT, DOUBLE, TIMESTAMP. <br> percentage: Target percentile, DOUBLE type. <br>Weighted Version: APPROX_PERCENTILE(x, w, percentage)<br>x: Column to compute. Supports all numeric types: INT32, INT64, FLOAT, DOUBLE, TIMESTAMP.<br>w: Weight column, integer type (must align with the length of x; NULL or 0 means the row is ignored).<br>percentage: Target percentile, DOUBLE type. | Same as the input column x. |
| SUM | Calculates the sum. | INT32 INT64 FLOAT DOUBLE | DOUBLE |
| AVG | Calculates the average. | INT32 INT64 FLOAT DOUBLE | DOUBLE |
| MAX | Finds the maximum value. | All types | Same as input type |
Expand Down Expand Up @@ -1244,7 +1244,7 @@ IoTDB:database1> select length, width, bitwise_right_shift_arithmetic(length,wid

## 7. Binary Functions

> Supported since V2.0.9-beta
> Supported since V2.0.10

### 7.1 Base64 Encoding Functions
| Function Name | Description | Input Type | Output Type |
Expand Down Expand Up @@ -1605,7 +1605,7 @@ The IF expression has two forms: one that specifies only the true value, and ano
| `IF(condition, true_value)` | If the condition evaluates to true, `true_value` is computed and returned; otherwise, `null` is returned and `true_value` is not evaluated. | — |
| `IF(condition, true_value, false_value)` | If the condition evaluates to true, `true_value` is computed and returned; otherwise, `false_value` is computed and returned. | The data types of `true_value` and `false_value` **must be exactly the same**. Implicit type conversion is not supported. |

> Supported since V2.0.9-beta
> Supported since V2.0.10

**Examples:**

Expand Down
2 changes: 1 addition & 1 deletion src/UserGuide/Master/Table/SQL-Manual/Common-Table-Expression_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@

CTE (Common Table Expressions) supports defining one or more temporary result sets (called common tables) using the `WITH` clause. These result sets can be referenced multiple times in subsequent parts of the same query. CTE provides a clean way to construct complex queries, making SQL code more readable and maintainable.

> Note: This feature is available since version 2.0.9-beta.
> Note: This feature is available since version 2.0.10.

## 2. Syntax Definition

Expand Down
2 changes: 1 addition & 1 deletion src/UserGuide/Master/Table/SQL-Manual/Set-Operations_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@

IoTDB natively supports standard SQL set operations, including three core operators: **UNION**, **INTERSECT**, and **EXCEPT**. These operations enable seamless merging, comparison, and filtering of query results from multiple time-series data sources, greatly improving the flexibility and efficiency of time-series data analysis.

> Note: This feature is available since version 2.0.9-beta.
> Note: This feature is available since version 2.0.10.

## 1. UNION
### 1.1 Overview
Expand Down
8 changes: 4 additions & 4 deletions src/UserGuide/Master/Table/Tools-System/Data-Export-Tool_apache.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ The data export tool `export-data.sh/bat` is located in the `tools` directory an
| `-h` | `--host` | Hostname of the IoTDB server. | No | `127.0.0.1` |
| `-p` | `--port` | Port number of the IoTDB server. | No | `6667` |
| `-u` | `--username` | Username for authentication. | No | `root` |
| `-pw` | `--password` | Password for authentication. Supported for hidden input since V2.0.9-beta | No | `root` |
| `-pw` | `--password` | Password for authentication. Supported for hidden input since V2.0.10 | No | `root` |
| `-sql_dialect` | `--sql_dialect` | Select server model : tree or table | No | tree |
| `-db ` | `--database` | The target database to be exported only takes effect when `-sql_dialect` is of the table type. | Yes when `-sql_dialect = table`| - |
| `-table` | `--table` | The target table to be exported only takes effect when `-sql_dialect` is of the table type. If the `-q` parameter is specified, this parameter will not take effect. If the export type is tsfile/sql, this parameter is mandatory. | ​ No | - |
Expand All @@ -45,9 +45,9 @@ The data export tool `export-data.sh/bat` is located in the `tools` directory an
| `-q` | `--query` | SQL query command to execute. Starting from v2.0.8, semicolons in SQL statements are automatically removed, and query execution proceeds normally. | No | - |
| `-timeout` | `--query_timeout` | Query timeout in milliseconds (ms). | No | `-1` (before v2.0.8)<br>`Long.MAX_VALUE` (v2.0.8 and later)<br>(Range: `-1~Long.MAX_VALUE`) |
| `-help` | `--help` | Display help information. | No | - |
| `-usessl` | `--use_ssl` | Use SSL protocol. Supported since V2.0.9-beta | No | - |
| `-ts` | `--trust_store` | Trust store. Supports hidden input. Supported since V2.0.9-beta | No | - |
| `-tpw` | `--trust_store_password` | Trust store password. Supports hidden input. Supported since V2.0.9-beta | No | - |
| `-usessl` | `--use_ssl` | Use SSL protocol. Supported since V2.0.10 | No | - |
| `-ts` | `--trust_store` | Trust store. Supports hidden input. Supported since V2.0.10 | No | - |
| `-tpw` | `--trust_store_password` | Trust store password. Supports hidden input. Supported since V2.0.10 | No | - |

### 2.2 CSV Format
#### 2.2.1 Command
Expand Down
Loading
Loading