diff --git a/src/UserGuide/latest-Table/AI-capability/AINode_apache.md b/src/UserGuide/latest-Table/AI-capability/AINode_apache.md index ad351c0f2..4c65c687c 100644 --- a/src/UserGuide/latest-Table/AI-capability/AINode_apache.md +++ b/src/UserGuide/latest-Table/AI-capability/AINode_apache.md @@ -105,21 +105,21 @@ Detailed meanings of SQL parameters: - **Model configuration file**: Parameters related to the model structure provided during registration, which must include input and output dimensions for inference: - | **Parameter Name** | **Description** | **Example** | - | ------------ | ---------------------------- | -------- | - | input_shape | Rows and columns of model input | [96,2] | - | output_shape | Rows and columns of model output | [48,2] | + | **Parameter Name** | **Description** | **Example** | + | ------------------ | -------------------------------- | ----------- | + | input_shape | Rows and columns of model input | [96,2] | + | output_shape | Rows and columns of model output | [48,2] | In addition to inference, data types of input and output can also be specified: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | ------------------------- | ---------------------- | | input_type | Data type of model input | ['float32', 'float32'] | | output_type | Data type of model output | ['float32', 'float32'] | Additional notes can be specified for model management display: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | --------------------------------------------- | -------------------------------------------- | | attributes | Optional notes set by users for model display | 'model_type': 'dlinear', 'kernel_size': '25' | @@ -407,4 +407,4 @@ AINode uses IoTDB's authentication for permission management. Users need `USE_MO | initialization_method | Initialization method: - `"estimated"`: Fit to estimate initial states - `"heuristic"`: Use heuristic for initial level/trend/season - `"known"`: User-provided initial values - `"legacy-heuristic"`: Legacy compatibility | "estimated" | | optimized | Optimize parameters via maximum likelihood. | True | | remove_bias | Remove bias to make residuals' mean zero. | False | -| use_brute | Use brute-force grid search for initial parameters. | | \ No newline at end of file +| use_brute | Use brute-force grid search for initial parameters. | | diff --git a/src/UserGuide/latest-Table/AI-capability/AINode_timecho.md b/src/UserGuide/latest-Table/AI-capability/AINode_timecho.md index 3a1570f60..d31d879b2 100644 --- a/src/UserGuide/latest-Table/AI-capability/AINode_timecho.md +++ b/src/UserGuide/latest-Table/AI-capability/AINode_timecho.md @@ -104,21 +104,21 @@ Detailed meanings of SQL parameters: - **Model configuration file**: Parameters related to the model structure provided during registration, which must include input and output dimensions for inference: - | **Parameter Name** | **Description** | **Example** | - | ------------ | ---------------------------- | -------- | - | input_shape | Rows and columns of model input | [96,2] | - | output_shape | Rows and columns of model output | [48,2] | + | **Parameter Name** | **Description** | **Example** | + | ------------------ | -------------------------------- | ----------- | + | input_shape | Rows and columns of model input | [96,2] | + | output_shape | Rows and columns of model output | [48,2] | In addition to inference, data types of input and output can also be specified: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | ------------------------- | ---------------------- | | input_type | Data type of model input | ['float32', 'float32'] | | output_type | Data type of model output | ['float32', 'float32'] | Additional notes can be specified for model management display: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | --------------------------------------------- | -------------------------------------------- | | attributes | Optional notes set by users for model display | 'model_type': 'dlinear', 'kernel_size': '25' | @@ -479,4 +479,4 @@ AINode uses IoTDB's authentication for permission management. Users need `USE_MO | initialization_method | Initialization method: - `"estimated"`: Fit to estimate initial states - `"heuristic"`: Use heuristic for initial level/trend/season - `"known"`: User-provided initial values - `"legacy-heuristic"`: Legacy compatibility | "estimated" | | optimized | Optimize parameters via maximum likelihood. | True | | remove_bias | Remove bias to make residuals' mean zero. | False | -| use_brute | Use brute-force grid search for initial parameters. | | \ No newline at end of file +| use_brute | Use brute-force grid search for initial parameters. | | diff --git a/src/UserGuide/latest-Table/API/Programming-Python-Native-API_timecho.md b/src/UserGuide/latest-Table/API/Programming-Python-Native-API_timecho.md index 4dd1fe4ff..364bb31ba 100644 --- a/src/UserGuide/latest-Table/API/Programming-Python-Native-API_timecho.md +++ b/src/UserGuide/latest-Table/API/Programming-Python-Native-API_timecho.md @@ -70,7 +70,7 @@ if has_next: | Function Name | Description | Parameters | Return Value | |---------------|-------------|------------|--------------| -| `encode_object_cell` | Encodes a single OBJECT cell into wire-format bytes | `is_eof: bool`,
`offset: int`,
`content: bytes` | `bytes`: `|[eof 1B]|[offset 8B BE]|[payload]|` | +| `encode_object_cell` | Encodes a single OBJECT cell into wire-format bytes | `is_eof: bool`,
`offset: int`,
`content: bytes` | `bytes`: `\|[eof 1B]\|[offset 8B BE]\|[payload]\|` | | `decode_object_cell` | Parses a wire-format cell back into `eof`, `offset`, and `payload` | `cell: bytes` (length ≥ 9) | `Tuple[bool, int, bytes]`: `(is_eof, offset, payload)` | | `Tablet.add_value_object` | Writes an OBJECT cell at the specified row and column (internally calls `encode_object_cell`) | `row_index: int`,
`column_index: int`,
`is_eof: bool`,
`offset: int`,
`content: bytes` | `None` | | `Tablet.add_value_object_by_name` | Same as above, locates column by name | `column_name: str`,
`row_index: int`,
`is_eof: bool`,
`offset: int`,
`content: bytes` | `None` | @@ -749,4 +749,4 @@ def test_table_numpy_tablet_object_columns(table_session): if __name__ == "__main__": pytest.main([__file__, "-v", "-rs"]) -``` \ No newline at end of file +``` diff --git a/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md b/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md index 20e4b147f..7b07287e3 100644 --- a/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md +++ b/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md @@ -31,7 +31,7 @@ The schema export tool `export-schema.sh/bat` is located in the `tools` director | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------|--------------------------|--------------------------------------------------------------------------| ------------------------------------- |---------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password. Supported for hidden input since V2.0.9-beta | No | root | diff --git a/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md b/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md index acb88afa2..f01e67169 100644 --- a/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md +++ b/src/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md @@ -31,7 +31,7 @@ The schema export tool `export-schema.sh/bat` is located in the `tools` director | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------|----------------------------|-----------------------------------------------------------------------| ------------------------------------- |-----------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password, Supported for hidden input since V2.0.9.1 | No | `TimechoDB@2021`(Before V2.0.6 it is root) | diff --git a/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md b/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md index 9a0d52853..8b7340d9e 100644 --- a/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md +++ b/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md @@ -31,7 +31,7 @@ The schema import tool `import-schema.sh/bat` is located in `tools` directory. | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------|---------------------------|--------------------------------------------------------------------------| ---------- |-------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password. Supported for hidden input since V2.0.9-beta | No | root | diff --git a/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md b/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md index 929cc3011..4b0af24c3 100644 --- a/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md +++ b/src/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md @@ -31,7 +31,7 @@ The schema import tool `import-schema.sh/bat` is located in `tools` directory. | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------| ------------------------------- |-----------------------------------------------------------------------| ---------- |----------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password, Supported for hidden input since V2.0.9.1 | No | `TimechoDB@2021`(Before V2.0.6 it is root) | diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md index 60ad52ddb..adc6a2f76 100644 --- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md @@ -84,22 +84,22 @@ By declaratively configuring these three parts in an SQL statement, flexible dat - The `pipe` and `pipe plugins` for tree modes and table modes are designed to be isolated from each other. Before creating a `pipe`, it is recommended to first use the `show` command to query the built-in plugins available under the current `-sql_dialect` parameter configuration to ensure syntax compatibility and functional support. - When Pipe fails to write data to the sink due to field type mismatches, IoTDB automatically converts the data to the field types defined in the existing sink schema and retries the write operation to improve synchronization success rate. This feature is controlled by the parameter `sink.exception.data.convert-on-type-mismatch`. Refer to the subsequent sink parameter table for detailed parameter descriptions. - * The conversion rules for type mismatches are as follows: - - | Source Type | Target Type | Conversion Rule | - |---------------------|-------------|---------------------------------------------------------------------------------| - | Numeric Type | Numeric Type| Convert to the target numeric type. Truncation, precision loss or overflow may occur. | - | Numeric Type | BOOLEAN | `0` is converted to `false`; non-zero values are converted to `true`. | - | BOOLEAN | Numeric Type| `true` is converted to `1`; `false` is converted to `0`. | - | TEXT, STRING, BLOB | BOOLEAN | Parse the string into a BOOLEAN value. | - | TEXT, STRING, BLOB | Numeric Type| Parse the string into the target numeric type. If parsing fails, write the default value `0`, `0L` or `0.0`. | - | TEXT, STRING, BLOB | TIMESTAMP | Parse the string into a TIMESTAMP value. If parsing fails, write the default value `0L`. | - | TEXT, STRING, BLOB | DATE | Parse the string into a DATE value. If parsing fails, write the default date `1970-01-01`. | - | Invalid Numeric Value | DATE | If conversion to a valid DATE fails, write the default date `1970-01-01`. | - | DATE | TIMESTAMP | Convert to the timestamp of 00:00 (UTC) on the same day. | - | TIMESTAMP | DATE | Convert to the corresponding date in UTC. | - - > **Note**: Automatic conversion is performed based on the existing sink schema and will **not** modify the sink schema. This feature prioritizes continuous data synchronization, which may result in precision loss or writing of default values. +The conversion rules for type mismatches are as follows: + +| Source Type | Target Type | Conversion Rule | +| --------------------- | ------------ | --------------- | +| Numeric Type | Numeric Type | Convert to the target numeric type. Truncation, precision loss, or overflow may occur. | +| Numeric Type | BOOLEAN | `0` is converted to `false`; non-zero values are converted to `true`. | +| BOOLEAN | Numeric Type | `true` is converted to `1`; `false` is converted to `0`. | +| TEXT, STRING, BLOB | BOOLEAN | Parse the string into a BOOLEAN value. | +| TEXT, STRING, BLOB | Numeric Type | Parse the string into the target numeric type. If parsing fails, write the default value `0`, `0L`, or `0.0`. | +| TEXT, STRING, BLOB | TIMESTAMP | Parse the string into a TIMESTAMP value. If parsing fails, write the default value `0L`. | +| TEXT, STRING, BLOB | DATE | Parse the string into a DATE value. If parsing fails, write the default date `1970-01-01`. | +| Invalid Numeric Value | DATE | If conversion to a valid DATE fails, write the default date `1970-01-01`. | +| DATE | TIMESTAMP | Convert to the timestamp of 00:00 (UTC) on the same day. | +| TIMESTAMP | DATE | Convert to the corresponding date in UTC. | + +> **Note**: Automatic conversion is performed based on the existing sink schema and will **not** modify the sink schema. This feature prioritizes continuous data synchronization, which may result in precision loss or writing of default values. ## 2. Usage Instructions diff --git a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md index f62a412b3..8e6964a35 100644 --- a/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md @@ -84,22 +84,22 @@ By declaratively configuring these three parts in an SQL statement, flexible dat - Object-type data export is supported since version V2.0.9.2. - When Pipe fails to write data to the sink due to field type mismatches, IoTDB automatically converts the data to the field types defined in the existing sink schema and retries the write operation to improve synchronization success rate. This feature is controlled by the parameter `sink.exception.data.convert-on-type-mismatch`. Refer to the subsequent sink parameter table for detailed parameter descriptions. - * The conversion rules for type mismatches are as follows: - - | Source Type | Target Type | Conversion Rule | - |---------------------|-------------|---------------------------------------------------------------------------------| - | Numeric Type | Numeric Type| Convert to the target numeric type. Truncation, precision loss or overflow may occur. | - | Numeric Type | BOOLEAN | `0` is converted to `false`; non-zero values are converted to `true`. | - | BOOLEAN | Numeric Type| `true` is converted to `1`; `false` is converted to `0`. | - | TEXT, STRING, BLOB | BOOLEAN | Parse the string into a BOOLEAN value. | - | TEXT, STRING, BLOB | Numeric Type| Parse the string into the target numeric type. If parsing fails, write the default value `0`, `0L` or `0.0`. | - | TEXT, STRING, BLOB | TIMESTAMP | Parse the string into a TIMESTAMP value. If parsing fails, write the default value `0L`. | - | TEXT, STRING, BLOB | DATE | Parse the string into a DATE value. If parsing fails, write the default date `1970-01-01`. | - | Invalid Numeric Value | DATE | If conversion to a valid DATE fails, write the default date `1970-01-01`. | - | DATE | TIMESTAMP | Convert to the timestamp of 00:00 (UTC) on the same day. | - | TIMESTAMP | DATE | Convert to the corresponding date in UTC. | - - > **Note**: Automatic conversion is performed based on the existing sink schema and will **not** modify the sink schema. This feature prioritizes continuous data synchronization, which may result in precision loss or writing of default values. +The conversion rules for type mismatches are as follows: + +| Source Type | Target Type | Conversion Rule | +| --------------------- | ------------ | --------------- | +| Numeric Type | Numeric Type | Convert to the target numeric type. Truncation, precision loss, or overflow may occur. | +| Numeric Type | BOOLEAN | `0` is converted to `false`; non-zero values are converted to `true`. | +| BOOLEAN | Numeric Type | `true` is converted to `1`; `false` is converted to `0`. | +| TEXT, STRING, BLOB | BOOLEAN | Parse the string into a BOOLEAN value. | +| TEXT, STRING, BLOB | Numeric Type | Parse the string into the target numeric type. If parsing fails, write the default value `0`, `0L`, or `0.0`. | +| TEXT, STRING, BLOB | TIMESTAMP | Parse the string into a TIMESTAMP value. If parsing fails, write the default value `0L`. | +| TEXT, STRING, BLOB | DATE | Parse the string into a DATE value. If parsing fails, write the default date `1970-01-01`. | +| Invalid Numeric Value | DATE | If conversion to a valid DATE fails, write the default date `1970-01-01`. | +| DATE | TIMESTAMP | Convert to the timestamp of 00:00 (UTC) on the same day. | +| TIMESTAMP | DATE | Convert to the corresponding date in UTC. | + +> **Note**: Automatic conversion is performed based on the existing sink schema and will **not** modify the sink schema. This feature prioritizes continuous data synchronization, which may result in precision loss or writing of default values. diff --git a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md index 2c4bd4f20..6ea537aec 100644 --- a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md +++ b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_apache.md @@ -549,7 +549,7 @@ SHOW CONFIGURATION ON 1 WITH DESC; +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | name| value| default_value| description| +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| cluster_name| defaultCluster| defaultCluster| Used for indicate cluster name and distinguish different cluster. If you need to modify the cluster name, it's recommended to use 'set configuration "cluster_name=xxx"' sql. Manually modifying configuration file is not recommended, which may cause node restart fail.effectiveMode: hot_reload.Datatype: string| +| cluster_name| defaultCluster| defaultCluster| Used to indicate the cluster name and distinguish different clusters. To modify the cluster name, use the SQL statement 'set configuration "cluster_name=xxx"'. Manually modifying the configuration file is not recommended because it may cause node restart failure. effectiveMode: hot_reload. Datatype: string| | cn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710|For the first ConfigNode to start, cn_seed_config_node points to its own cn_internal_address:cn_internal_port. For other ConfigNodes that to join the cluster, cn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this ConfigNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | dn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710| dn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this DataNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | cn_internal_address| 127.0.0.1| 127.0.0.1| Used for RPC communication inside cluster. Could set 127.0.0.1(for local test) or ipv4 address.effectiveMode: first_start.Datatype: String| diff --git a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md index 9d1a95341..c58fccfd5 100644 --- a/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Maintenance-commands_timecho.md @@ -582,7 +582,7 @@ SHOW CONFIGURATION ON 1 WITH DESC; +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | name| value| default_value| description| +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| cluster_name| defaultCluster| defaultCluster| Used for indicate cluster name and distinguish different cluster. If you need to modify the cluster name, it's recommended to use 'set configuration "cluster_name=xxx"' sql. Manually modifying configuration file is not recommended, which may cause node restart fail.effectiveMode: hot_reload.Datatype: string| +| cluster_name| defaultCluster| defaultCluster| Used to indicate the cluster name and distinguish different clusters. To modify the cluster name, use the SQL statement 'set configuration "cluster_name=xxx"'. Manually modifying the configuration file is not recommended because it may cause node restart failure. effectiveMode: hot_reload. Datatype: string| | cn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710|For the first ConfigNode to start, cn_seed_config_node points to its own cn_internal_address:cn_internal_port. For other ConfigNodes that to join the cluster, cn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this ConfigNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | dn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710| dn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this DataNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | cn_internal_address| 127.0.0.1| 127.0.0.1| Used for RPC communication inside cluster. Could set 127.0.0.1(for local test) or ipv4 address.effectiveMode: first_start.Datatype: String| diff --git a/src/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md b/src/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md index eeab8753d..f97a66db5 100644 --- a/src/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md @@ -230,7 +230,7 @@ Used to specify which row to start the next pattern match from after identifying | ------------------------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------- | | `AFTER MATCH SKIP PAST LAST ROW` | Default behavior. Starts from the row after the last row of the current match. | No | | `AFTER MATCH SKIP TO NEXT ROW` | Starts from the second row in the current match. | Yes | -| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | Jumps to start from the [ first row | last row ] of a pattern variable. | Yes | +| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | Jumps to start from the [ first row \| last row ] of a pattern variable. | Yes | * Among all possible configurations, only when `ALL ROWS PER MATCH WITH UNMATCHED ROWS` is used in combination with `AFTER MATCH SKIP PAST LAST ROW` can the system ensure that exactly one output record is generated for each input row. diff --git a/src/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md b/src/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md index cb36c56f6..90ddd39de 100644 --- a/src/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md +++ b/src/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md @@ -232,7 +232,7 @@ Used to specify which row to start the next pattern match from after identifying | ------------------------------------------------------------- | -------------------------------------------------------------------------------- | ----------------------------- | | `AFTER MATCH SKIP PAST LAST ROW` | Default behavior. Starts from the row after the last row of the current match. | No | | `AFTER MATCH SKIP TO NEXT ROW` | Starts from the second row in the current match. | Yes | -| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | Jumps to start from the [ first row | last row ] of a pattern variable. | Yes | +| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | Jumps to start from the [ first row \| last row ] of a pattern variable. | Yes | * Among all possible configurations, only when `ALL ROWS PER MATCH WITH UNMATCHED ROWS` is used in combination with `AFTER MATCH SKIP PAST LAST ROW` can the system ensure that exactly one output record is generated for each input row. diff --git a/src/UserGuide/latest/AI-capability/AINode_apache.md b/src/UserGuide/latest/AI-capability/AINode_apache.md index 5771f07c6..c586ee380 100644 --- a/src/UserGuide/latest/AI-capability/AINode_apache.md +++ b/src/UserGuide/latest/AI-capability/AINode_apache.md @@ -108,21 +108,21 @@ Detailed meanings of SQL parameters: - **Model configuration file**: Parameters related to the model structure provided during registration, which must include input and output dimensions for inference: - | **Parameter Name** | **Description** | **Example** | - | ------------ | ---------------------------- | -------- | - | input_shape | Rows and columns of model input | [96,2] | - | output_shape | Rows and columns of model output | [48,2] | + | **Parameter Name** | **Description** | **Example** | + | ------------------ | -------------------------------- | ----------- | + | input_shape | Rows and columns of model input | [96,2] | + | output_shape | Rows and columns of model output | [48,2] | In addition to inference, data types of input and output can also be specified: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | ------------------------- | ---------------------- | | input_type | Data type of model input | ['float32', 'float32'] | | output_type | Data type of model output | ['float32', 'float32'] | Additional notes can be specified for model management display: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | --------------------------------------------- | -------------------------------------------- | | attributes | Optional notes set by users for model display | 'model_type': 'dlinear', 'kernel_size': '25' | @@ -621,4 +621,4 @@ We plot the results detected as anomalies to get the following image. Where the ![](/img/s6.png) -It can be seen that the Stray model has modelled the input sequence changes and successfully detected the time points where anomalies occur. \ No newline at end of file +It can be seen that the Stray model has modelled the input sequence changes and successfully detected the time points where anomalies occur. diff --git a/src/UserGuide/latest/AI-capability/AINode_timecho.md b/src/UserGuide/latest/AI-capability/AINode_timecho.md index 7ed02f520..7c8672e82 100644 --- a/src/UserGuide/latest/AI-capability/AINode_timecho.md +++ b/src/UserGuide/latest/AI-capability/AINode_timecho.md @@ -109,21 +109,21 @@ Detailed meanings of SQL parameters: - **Model configuration file**: Parameters related to the model structure provided during registration, which must include input and output dimensions for inference: - | **Parameter Name** | **Description** | **Example** | - | ------------ | ---------------------------- | -------- | - | input_shape | Rows and columns of model input | [96,2] | - | output_shape | Rows and columns of model output | [48,2] | + | **Parameter Name** | **Description** | **Example** | + | ------------------ | -------------------------------- | ----------- | + | input_shape | Rows and columns of model input | [96,2] | + | output_shape | Rows and columns of model output | [48,2] | In addition to inference, data types of input and output can also be specified: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | ------------------------- | ---------------------- | | input_type | Data type of model input | ['float32', 'float32'] | | output_type | Data type of model output | ['float32', 'float32'] | Additional notes can be specified for model management display: - | **Parameter Name** | **Description** | **Example** | + | **Parameter Name** | **Description** | **Example** | | ------------------ | --------------------------------------------- | -------------------------------------------- | | attributes | Optional notes set by users for model display | 'model_type': 'dlinear', 'kernel_size': '25' | @@ -690,4 +690,4 @@ We plot the results detected as anomalies to get the following image. Where the ![](/img/s6.png) -It can be seen that the Stray model has modelled the input sequence changes and successfully detected the time points where anomalies occur. \ No newline at end of file +It can be seen that the Stray model has modelled the input sequence changes and successfully detected the time points where anomalies occur. diff --git a/src/UserGuide/latest/Basic-Concept/Query-Data_apache.md b/src/UserGuide/latest/Basic-Concept/Query-Data_apache.md index 773767ebb..174108261 100644 --- a/src/UserGuide/latest/Basic-Concept/Query-Data_apache.md +++ b/src/UserGuide/latest/Basic-Concept/Query-Data_apache.md @@ -2985,7 +2985,7 @@ This statement specifies that `root.sg_copy.d1` is an unaligned device and `root ETL the original data and write a new time series. ```sql -SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEIVCE; +SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEVICE; ``` ``` +--------------+-------------------+---------------------------+--------+ diff --git a/src/UserGuide/latest/Basic-Concept/Query-Data_timecho.md b/src/UserGuide/latest/Basic-Concept/Query-Data_timecho.md index 3c9c40404..91c407083 100644 --- a/src/UserGuide/latest/Basic-Concept/Query-Data_timecho.md +++ b/src/UserGuide/latest/Basic-Concept/Query-Data_timecho.md @@ -2984,7 +2984,7 @@ This statement specifies that `root.sg_copy.d1` is an unaligned device and `root ETL the original data and write a new time series. ```sql -SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEIVCE; +SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEVICE; ``` ``` +--------------+-------------------+---------------------------+--------+ diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements.md b/src/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements.md index a909bec8c..009c0acca 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Environment-Requirements.md @@ -43,7 +43,7 @@ Only a few hard disks are installed on the server. Configure Raid5 directly. The recommended configurations are as follows: | **Use classification** | **Raid type** | **Disk number** | **Redundancy** | **Available capacity** | | ----------- | -------- | -------- | --------- | -------- | -| system/data disk | RAID5 | 4 | 1 | 3 | is allowed to fail| +| system/data disk | RAID5 | 4 | 1 is allowed to fail | 3 | - Example 2: Twelve 3.5-inch hard disks @@ -119,7 +119,8 @@ The following table lists the recommended disk partitioning methods. -### Network Configuration + +### 2.3 Network Configuration 1. Disable the firewall @@ -152,7 +153,7 @@ systemctl start sshd # Enable port 22 3. Ensure that servers are connected to each other -### 2.3 Other Configuration +### 2.4 Other Configuration 1. Reduce the system swap priority to the lowest level @@ -192,4 +193,4 @@ Vim ~/.bashrc # Configure the JDK environment } # Add JDK environment variables source ~/.bashrc # The configuration takes effect java -version # Check the JDK environment -``` \ No newline at end of file +``` diff --git a/src/UserGuide/latest/Deployment-and-Maintenance/Kubernetes_timecho.md b/src/UserGuide/latest/Deployment-and-Maintenance/Kubernetes_timecho.md index 14b51ab84..da93a7072 100644 --- a/src/UserGuide/latest/Deployment-and-Maintenance/Kubernetes_timecho.md +++ b/src/UserGuide/latest/Deployment-and-Maintenance/Kubernetes_timecho.md @@ -315,7 +315,7 @@ cd /iotdb/sbin # Exit the container ``` -### Option 3: Manual Activation +### 8.3 Option 3: Manual Activation 1. View ConfigNode details to determine the node: @@ -442,4 +442,4 @@ kubectl get pods -n iotdb-ns -o wide # datanode-1 1/1 Running 10 (5m42s ago) 75m 10.20.187.15 a87 # datanode-2 1/1 Running 10 (5m55s ago) 75m 10.20.191.76 a88 # datanode-3 1/1 Running 10 (5m55s ago) 75m 10.20.191.76 a88 -``` \ No newline at end of file +``` diff --git a/src/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md b/src/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md index 9a8405f52..5b36a9294 100644 --- a/src/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md +++ b/src/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md @@ -148,7 +148,7 @@ IOTDB_JMX_OPTS="$IOTDB_JMX_OPTS -XX:MaxGCPauseMillis=200" | storage\_tsdb\_retention\_time | The number of days to save data is 15 days by default | NO | | storage\_tsdb\_retention\_size | The data size that can be saved by the specified block defaults to 512M. Please note the units are KB, MB, GB, TB, PB, and EB. | NO | -If metrics are configured in `iotdb-system.properties` and `iotdb-system.properties` of config/xxx.yaml, the configuration will be automatically put into promethues without manual modification. +If metrics are configured in `iotdb-system.properties` and `iotdb-system.properties` of config/xxx.yaml, the configuration will be automatically put into Prometheus without manual modification. Note: How to configure the value corresponding to the yaml key to contain special characters such as: etc. It is recommended to use double quotes for the entire value, and do not use paths containing spaces in the corresponding file paths to prevent abnormal recognition problems. diff --git a/src/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md b/src/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md index 33973cbe5..027ffc49b 100644 --- a/src/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md +++ b/src/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md @@ -31,7 +31,7 @@ The schema export tool `export-schema.sh/bat` is located in the `tools` director | **Short Param** | **Full Param** | **Description** | Required | Default | |------------------|---------------------------|--------------------------------------------------------------------------| ------------------------------------- |-----------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password. Supported for hidden input since V2.0.9-beta | No | root | diff --git a/src/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md b/src/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md index 6ad9ae662..e68bfc67b 100644 --- a/src/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md +++ b/src/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md @@ -31,7 +31,7 @@ The schema export tool `export-schema.sh/bat` is located in the `tools` director | **Short Param** | **Full Param** | **Description** | Required | Default | |------------------|--------------------------| ------------------------------------------------------------------------ | ------------------------------------- |-----------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password, Supported for hidden input since V2.0.9.1 | No | TimechoDB@2021(Before V2.0.6 it is root) | diff --git a/src/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md b/src/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md index 1daf8dc0b..40bf42afa 100644 --- a/src/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md +++ b/src/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md @@ -31,7 +31,7 @@ The schema import tool `import-schema.sh/bat` is located in `tools` directory. | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------|---------------------------|--------------------------------------------------------------------------| ---------- |-------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password. Supported for hidden input since V2.0.9-beta | No | root | diff --git a/src/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md b/src/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md index 5d9de70a3..a41e516d4 100644 --- a/src/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md +++ b/src/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md @@ -31,7 +31,7 @@ The schema import tool `import-schema.sh/bat` is located in `tools` directory. | **Short Param** | **Full Param** | **Description** | Required | Default | |-----------------| ------------------------------- |-----------------------------------------------------------------------| ---------- |-------------------------------------------| -| `-h` | `-- host` | Hostname | No | 127.0.0.1 | +| `-h` | `--host` | Hostname | No | 127.0.0.1 | | `-p` | `--port` | Port number | No | 6667 | | `-u` | `--username` | Username | No | root | | `-pw` | `--password` | Password, Supported for hidden input since V2.0.9.1 | No | TimechoDB@2021(Before V2.0.6 it is root) | diff --git a/src/UserGuide/latest/User-Manual/Data-subscription_apache.md b/src/UserGuide/latest/User-Manual/Data-subscription_apache.md index 6fc310866..ed74b71b8 100644 --- a/src/UserGuide/latest/User-Manual/Data-subscription_apache.md +++ b/src/UserGuide/latest/User-Manual/Data-subscription_apache.md @@ -61,8 +61,7 @@ Detailed explanation of each parameter is as follows: | **path** | optional: `root.**` | The path of the time series data corresponding to the topic, representing a set of time series to be subscribed. | | **start-time** | optional: `MIN_VALUE` | The start time (event time) of the time series data corresponding to the topic. Can be in ISO format, such as 2011-12-03T10:15:30 or 2011-12-03T10:15:30+01:00, or a long value representing a raw timestamp consistent with the database's timestamp precision. Supports the special value `now`, which means the creation time of the topic. When start-time is `now` and end-time is MAX_VALUE, it indicates that only real-time data is subscribed. | | **end-time** | optional: `MAX_VALUE` | The end time (event time) of the time series data corresponding to the topic. Can be in ISO format, such as 2011-12-03T10:15:30 or 2011-12:03T10:15:30+01:00, or a long value representing a raw timestamp consistent with the database's timestamp precision. Supports the special value `now`, which means the creation time of the topic. When end-time is `now` and start-time is MIN_VALUE, it indicates that only historical data is subscribed. | -| **processor** | optional: `do-nothing-processor` | The name and parameter configuration of the processor plugin, representing the custom processing logic applied to the original subscribed data, which can be specified in a similar way to pipe processor plugins. - | +| **processor** | optional: `do-nothing-processor` | The name and parameter configuration of the processor plugin, representing the custom processing logic applied to the original subscribed data, which can be specified in a similar way to pipe processor plugins. | | **format** | optional: `SessionDataSetsHandler` | Represents the form in which data is subscribed from the topic. Currently supports the following two forms of data: `SessionDataSetsHandler`: Data subscribed from the topic is obtained using `SubscriptionSessionDataSetsHandler`, and consumers can consume each piece of data row by row. `TsFileHandler`: Data subscribed from the topic is obtained using `SubscriptionTsFileHandler`, and consumers can directly subscribe to the TsFile storing the corresponding data. | | **mode** **(supported in versions 1.3.3.2 and later)** | option: `live` | The subscription mode corresponding to the topic, with two options: `live`: When subscribing to this topic, the subscribed dataset mode is a dynamic dataset, which means that you can continuously consume the latest data. `snapshot`: When the consumer subscribes to this topic, the subscribed dataset mode is a static dataset, which means the snapshot of the data at the moment the consumer group subscribes to the topic (not the moment the topic is created); the formed static dataset after subscription does not support TTL.| | **loose-range** **(supported in versions 1.3.3.2 and later)** | option: `""` | String: Whether to strictly filter the data corresponding to this topic according to the path and time range, for example: "": Strictly filter the data corresponding to this topic according to the path and time range. `"time"`: Do not strictly filter the data corresponding to this topic according to the time range (rough filter); strictly filter the data corresponding to this topic according to the path. `"path"`: Do not strictly filter the data corresponding to this topic according to the path (rough filter); strictly filter the data corresponding to this topic according to the time range. `"time, path"` / `"path, time"` / `"all"`: Do not strictly filter the data corresponding to this topic according to the path and time range (rough filter).| @@ -145,4 +144,4 @@ In addition to SQL statements, IoTDB also supports using data subscription featu 2. Message Delivery Semantics - Kafka can achieve Exactly once semantics for both Producers and Consumers through configuration. -- The IoTDB subscription client currently cannot provide Exactly once semantics for Consumers. \ No newline at end of file +- The IoTDB subscription client currently cannot provide Exactly once semantics for Consumers. diff --git a/src/UserGuide/latest/User-Manual/Data-subscription_timecho.md b/src/UserGuide/latest/User-Manual/Data-subscription_timecho.md index 2d13c01b8..2012b92a8 100644 --- a/src/UserGuide/latest/User-Manual/Data-subscription_timecho.md +++ b/src/UserGuide/latest/User-Manual/Data-subscription_timecho.md @@ -61,8 +61,7 @@ Detailed explanation of each parameter is as follows: | **path** | optional: `root.**` | The path of the time series data corresponding to the topic, representing a set of time series to be subscribed. | | **start-time** | optional: `MIN_VALUE` | The start time (event time) of the time series data corresponding to the topic. Can be in ISO format, such as 2011-12-03T10:15:30 or 2011-12-03T10:15:30+01:00, or a long value representing a raw timestamp consistent with the database's timestamp precision. Supports the special value `now`, which means the creation time of the topic. When start-time is `now` and end-time is MAX_VALUE, it indicates that only real-time data is subscribed. | | **end-time** | optional: `MAX_VALUE` | The end time (event time) of the time series data corresponding to the topic. Can be in ISO format, such as 2011-12-03T10:15:30 or 2011-12:03T10:15:30+01:00, or a long value representing a raw timestamp consistent with the database's timestamp precision. Supports the special value `now`, which means the creation time of the topic. When end-time is `now` and start-time is MIN_VALUE, it indicates that only historical data is subscribed. | -| **processor** | optional: `do-nothing-processor` | The name and parameter configuration of the processor plugin, representing the custom processing logic applied to the original subscribed data, which can be specified in a similar way to pipe processor plugins. - | +| **processor** | optional: `do-nothing-processor` | The name and parameter configuration of the processor plugin, representing the custom processing logic applied to the original subscribed data, which can be specified in a similar way to pipe processor plugins. | | **format** | optional: `SessionDataSetsHandler` | Represents the form in which data is subscribed from the topic. Currently supports the following two forms of data: `SessionDataSetsHandler`: Data subscribed from the topic is obtained using `SubscriptionSessionDataSetsHandler`, and consumers can consume each piece of data row by row. `TsFileHandler`: Data subscribed from the topic is obtained using `SubscriptionTsFileHandler`, and consumers can directly subscribe to the TsFile storing the corresponding data. | | **mode** **(supported in versions 1.3.3.2 and later)** | option: `live` | The subscription mode corresponding to the topic, with two options: `live`: When subscribing to this topic, the subscribed dataset mode is a dynamic dataset, which means that you can continuously consume the latest data. `snapshot`: When the consumer subscribes to this topic, the subscribed dataset mode is a static dataset, which means the snapshot of the data at the moment the consumer group subscribes to the topic (not the moment the topic is created); the formed static dataset after subscription does not support TTL.| | **loose-range** **(supported in versions 1.3.3.2 and later)** | option: `""` | String: Whether to strictly filter the data corresponding to this topic according to the path and time range, for example: "": Strictly filter the data corresponding to this topic according to the path and time range. `"time"`: Do not strictly filter the data corresponding to this topic according to the time range (rough filter); strictly filter the data corresponding to this topic according to the path. `"path"`: Do not strictly filter the data corresponding to this topic according to the path (rough filter); strictly filter the data corresponding to this topic according to the time range. `"time, path"` / `"path, time"` / `"all"`: Do not strictly filter the data corresponding to this topic according to the path and time range (rough filter).| @@ -145,4 +144,4 @@ In addition to SQL statements, IoTDB also supports using data subscription featu 2. Message Delivery Semantics - Kafka can achieve Exactly once semantics for both Producers and Consumers through configuration. -- The IoTDB subscription client currently cannot provide Exactly once semantics for Consumers. \ No newline at end of file +- The IoTDB subscription client currently cannot provide Exactly once semantics for Consumers. diff --git a/src/zh/UserGuide/latest-Table/AI-capability/AINode_apache.md b/src/zh/UserGuide/latest-Table/AI-capability/AINode_apache.md index 5097e3ed9..48e001dbc 100644 --- a/src/zh/UserGuide/latest-Table/AI-capability/AINode_apache.md +++ b/src/zh/UserGuide/latest-Table/AI-capability/AINode_apache.md @@ -98,23 +98,23 @@ SQL中参数的具体含义如下： - 模型配置文件：模型注册时需要提供的与模型结构有关的参数，其中必须包含模型的输入输出维度用于模型推理： - - | **参数名** | **参数描述** | **示例** | - | ------------ | ---------------------------- | -------- | - | input_shape | 模型输入的行列，用于模型推理 | [96,2] | - | output_shape | 模型输出的行列，用于模型推理 | [48,2] | + | **参数名** | **参数描述** | **示例** | + | ------------ | ---------------------------- | -------- | + | input_shape | 模型输入的行列，用于模型推理 | [96,2] | + | output_shape | 模型输出的行列，用于模型推理 | [48,2] | 除了模型推理外，还可以指定模型输入输出的数据类型： - - | **参数名** | **参数描述** | **示例** | - | ----------- | ------------------ | --------------------- | - | input_type | 模型输入的数据类型 | ['float32','float32'] | - | output_type | 模型输出的数据类型 | ['float32','float32'] | + | **参数名** | **参数描述** | **示例** | + | ----------- | ------------------ | --------------------- | + | input_type | 模型输入的数据类型 | ['float32','float32'] | + | output_type | 模型输出的数据类型 | ['float32','float32'] | - 除此之外，可以额外指定备注信息用于在模型管理时进行展示 + 除此之外，可以额外指定备注信息用于在模型管理时进行展示 - - | **参数名** | **参数描述** | **示例** | - | ---------- | ---------------------------------------------- | ------------------------------------------- | - | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | + | **参数名** | **参数描述** | **示例** | + | ---------- | ---------------------------------------------- | ------------------------------------------- | + | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | 除了本地模型文件的注册，还可以通过URI来指定远程资源路径来进行注册，使用开源的模型仓库（例如HuggingFace）。 @@ -381,4 +381,4 @@ AINode 目前支持多种时序大模型，部署使用请参考[时序大模型 | initialization_method | 初始化方法： • `"estimated"`：通过拟合估计初始状态 • `"heuristic"`：使用启发式方法估计初始水平/趋势/季节 • `"known"`：用户显式提供所有初始值 • `"legacy-heuristic"`：旧版本兼容方式 | "estimated" | | optmized | 是否通过最大化对数似然来优化参数。 | True | | remove_bias | 是否移除偏差，使预测值和拟合值的残差平均值为0。 | False | -| use_brute | 是否使用穷举法（网格搜索）来寻找初始参数。否则使用启发式初始值。 | | \ No newline at end of file +| use_brute | 是否使用穷举法（网格搜索）来寻找初始参数。否则使用启发式初始值。 | | diff --git a/src/zh/UserGuide/latest-Table/AI-capability/AINode_timecho.md b/src/zh/UserGuide/latest-Table/AI-capability/AINode_timecho.md index d28e42606..1cefe4f43 100644 --- a/src/zh/UserGuide/latest-Table/AI-capability/AINode_timecho.md +++ b/src/zh/UserGuide/latest-Table/AI-capability/AINode_timecho.md @@ -98,23 +98,23 @@ SQL中参数的具体含义如下： - 模型配置文件：模型注册时需要提供的与模型结构有关的参数，其中必须包含模型的输入输出维度用于模型推理： - - | **参数名** | **参数描述** | **示例** | - | ------------ | ---------------------------- | -------- | - | input_shape | 模型输入的行列，用于模型推理 | [96,2] | - | output_shape | 模型输出的行列，用于模型推理 | [48,2] | + | **参数名** | **参数描述** | **示例** | + | ------------ | ---------------------------- | -------- | + | input_shape | 模型输入的行列，用于模型推理 | [96,2] | + | output_shape | 模型输出的行列，用于模型推理 | [48,2] | - - ​ 除了模型推理外，还可以指定模型输入输出的数据类型： + 除了模型推理外，还可以指定模型输入输出的数据类型： - - | **参数名** | **参数描述** | **示例** | - | ----------- | ------------------ | --------------------- | - | input_type | 模型输入的数据类型 | ['float32','float32'] | - | output_type | 模型输出的数据类型 | ['float32','float32'] | + | **参数名** | **参数描述** | **示例** | + | ----------- | ------------------ | --------------------- | + | input_type | 模型输入的数据类型 | ['float32','float32'] | + | output_type | 模型输出的数据类型 | ['float32','float32'] | - - ​ 除此之外，可以额外指定备注信息用于在模型管理时进行展示 + 除此之外，可以额外指定备注信息用于在模型管理时进行展示 - - | **参数名** | **参数描述** | **示例** | - | ---------- | ---------------------------------------------- | ------------------------------------------- | - | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | + | **参数名** | **参数描述** | **示例** | + | ---------- | ---------------------------------------------- | ------------------------------------------- | + | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | 除了本地模型文件的注册，还可以通过URI来指定远程资源路径来进行注册，使用开源的模型仓库（例如HuggingFace）。 @@ -450,4 +450,4 @@ AINode 目前支持多种时序大模型，部署使用请参考[时序大模型 | initialization_method | 初始化方法： • `"estimated"`：通过拟合估计初始状态 • `"heuristic"`：使用启发式方法估计初始水平/趋势/季节 • `"known"`：用户显式提供所有初始值 • `"legacy-heuristic"`：旧版本兼容方式 | "estimated" | | optmized | 是否通过最大化对数似然来优化参数。 | True | | remove_bias | 是否移除偏差，使预测值和拟合值的残差平均值为0。 | False | -| use_brute | 是否使用穷举法（网格搜索）来寻找初始参数。否则使用启发式初始值。 | | \ No newline at end of file +| use_brute | 是否使用穷举法（网格搜索）来寻找初始参数。否则使用启发式初始值。 | | diff --git a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md index e1af1e1d0..99712b134 100644 --- a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md +++ b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md @@ -148,7 +148,7 @@ IoTDB> show models ### 附录 -**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) +**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) **[2]** TIMER-XL- LONG-CONTEXT TRANSFORMERS FOR UNIFIED TIME SERIES FORECASTING ,Yong Liu, Guo Qin, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref2) diff --git a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md index 3d86bfc4f..953b3ed9a 100644 --- a/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest-Table/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md @@ -148,7 +148,7 @@ IoTDB> show models ### 附录 -**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) +**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) **[2]** TIMER-XL- LONG-CONTEXT TRANSFORMERS FOR UNIFIED TIME SERIES FORECASTING ,Yong Liu, Guo Qin, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref2) diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index adb5f6979..e57726491 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index 7b865ecc3..fa8e0f176 100644 --- a/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest-Table/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -289,6 +289,6 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_timecho.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_timecho.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.6】小节。 diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md index ad1ef7db3..6926c3f07 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_apache.md @@ -34,7 +34,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |--------------|------------------------| ----------------------------------------------------------------- | -------------- |---------------------------------------------------------------------------| | -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md index df86ca8d4..f171f61d9 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Export-Tool_timecho.md @@ -41,7 +41,7 @@ IoTDB 支持两种方式进行数据导出： | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |--------------|-------------------------|--------------------------------------------------------------------------------------| -------------- |-----------------------------------------------------------------------------| | -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6 版本之前为 root) | diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md index 48bd3a566..b72fa0561 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_apache.md @@ -45,18 +45,18 @@ IoTDB 支持三种方式进行数据导入： | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |--------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------| -------------- |----------------------------------| -| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | -| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为 csv sql tsfile 这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | +| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为 csv sql tsfile 这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | | | -sql_dialect | --sql_dialect | 选择 server 是树模型还是表模型，当前支持 tree 和 table 类型 | 否 | tree | | -db | --database | 数据将要导入的目标库，只在 `-sql_dialect` 为 table 类型下生效。 |-sql_dialect 为 table 时必填；
V2.0.9-beta 版本起，当文件格式为 SQL 时，该参数为可选参数，若参数或 SQL 中均未显式指定目标数据库时会进行提示。 | - | | -table | --table | 数据将要导入的目标表，只在 `-sql_dialect` 为 table 类型且文件类型为 csv 条件下生效且必填。 | 否 | - | | -tn | --thread\_num | 最大并行线程数 | 否 | 8
范围：0～Integer.Max=2147483647 | | -tz | --timezone | 时区设置，例如`+08:00`或`-01:00` | 否 | 本机系统时间 | -| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | +| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | | | -usessl | --use_ssl | 使用 SSL 协议，自 V2.0.9-beta 起支持 | 否 | - | | -ts | --trust_store | 信任库。支持隐藏输入，自 V2.0.9-beta 起支持 | 否 | - | | -tpw | --trust_store_password | 信任库密码。支持隐藏输入，自 V2.0.9-beta 起支持 | 否 | - | @@ -99,8 +99,7 @@ IoTDB 支持三种方式进行数据导入： | -aligned | --use\_aligned | 是否导入为对齐序列 | 否 | false | | -batch | --batch\_size | 指定每调用一次接口处理的数据行数（最小值为1，最大值为Integer.​*MAX\_VALUE*​） | 否 | 100000
范围：0～Integer.Max=2147483647 | | -ti | --type\_infer | 通过选项定义类型信息，例如`"boolean=text,int=long, ..."` | 否 | 无 | -| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms -| +| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms | #### 2.2.3 运行示例 @@ -210,7 +209,7 @@ Fail to insert measurements '[column.name]' caused by [data type is not consiste | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | ---------- | ------------------------ |----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -------------------- | | -os| --on\_succcess| 1. none：不删除
2. mv：移动成功的文件到目标文件夹
3. cp：硬连接（拷贝）成功的文件到目标文件夹
4. delete：删除 | √ || -| -sd | --success\_dir | 当`--on_succcess`为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_succcess`为mv或cp时需要填写 | `${EXEC_DIR}/success`| +| -sd | --success\_dir | 当`--on_success`为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_success`为mv或cp时需要填写 | `${EXEC_DIR}/success`| | -of| --on\_fail| 1. none：跳过
2. mv：移动失败的文件到目标文件夹
3. cp：硬连接（拷贝）失败的文件到目标文件夹
4. delete：删除 | √ || | -fd | --fail\_dir | 当`--on_fail`指定为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_fail`指定为 mv 或 cp 时需要填写 | `${EXEC_DIR}/fail` | | -tp | --timestamp\_precision | 时间戳精度
tsfile 非远程导入：-tp 指定 tsfile 文件的时间精度 手动校验和服务器的时间戳是否一致 不一致返回报错信息
远程导入：-tp 指定 tsfile 文件的时间精度 pipe 自动校验时间戳精度是否一致 不一致返回 pipe 报错信息 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms| diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md index aa235621b..71105b603 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Data-Import-Tool_timecho.md @@ -46,18 +46,18 @@ IoTDB 支持三种方式进行数据导入： | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |--------------|-------------------------|-------------------------------------------------------------------------------------------------------------------------------| -------------- |-------------------------------------| -| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6 版本之前为 root) | -| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为 csv sql tsfile 这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | +| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为 csv sql tsfile 这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | | | -sql_dialect | --sql_dialect | 选择 server 是树模型还是表模型，当前支持 tree 和 table 类型 | 否 | tree | | -db | --database | 数据将要导入的目标库，只在 `-sql_dialect` 为 table 类型下生效。 |-sql_dialect 为 table 时必填；
V2.0.9.2 版本起，当文件格式为 SQL 时，该参数为可选参数，若参数或 SQL 中均未显式指定目标数据库时会进行提示。 | - | | -table | --table | 数据将要导入的目标表，只在 `-sql_dialect` 为 table 类型且文件类型为 csv 条件下生效且必填。 | 否 | - | | -tn | --thread\_num | 最大并行线程数 | 否 | 8
范围：0～Integer.Max=2147483647 | | -tz | --timezone | 时区设置，例如`+08:00`或`-01:00` | 否 | 本机系统时间 | -| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | +| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | | | -usessl | --use_ssl | 使用 SSL 协议，自 V2.0.9.1 起支持 | 否 | - | | -ts | --trust_store | 信任库。支持隐藏输入，自 V2.0.9.1 起支持 | 否 | - | | -tpw | --trust_store_password | 信任库密码。支持隐藏输入，自 V2.0.9.1 起支持 | 否 | - | @@ -100,8 +100,7 @@ IoTDB 支持三种方式进行数据导入： | -aligned | --use\_aligned | 是否导入为对齐序列 | 否 | false | | -batch | --batch\_size | 指定每调用一次接口处理的数据行数（最小值为1，最大值为Integer.​*MAX\_VALUE*​） | 否 | 100000
范围：0～Integer.Max=2147483647 | | -ti | --type\_infer | 通过选项定义类型信息，例如`"boolean=text,int=long, ..."` | 否 | 无 | -| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms -| +| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms | #### 2.2.3 运行示例 @@ -211,7 +210,7 @@ Fail to insert measurements '[column.name]' caused by [data type is not consiste | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |------|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -------------------- | | -os | --on\_succcess | 1. none：不删除
2. mv：移动成功的文件到目标文件夹
3. cp：硬连接（拷贝）成功的文件到目标文件夹
4. delete：删除 | √ || -| -sd | --success\_dir | 当`--on_succcess`为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_succcess`为mv或cp时需要填写 | `${EXEC_DIR}/success`| +| -sd | --success\_dir | 当`--on_success`为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_success`为mv或cp时需要填写 | `${EXEC_DIR}/success`| | -of | --on\_fail | 1. none：跳过
2. mv：移动失败的文件到目标文件夹
3. cp：硬连接（拷贝）失败的文件到目标文件夹
4. delete：删除 | √ || | -fd | --fail\_dir | 当`--on_fail`指定为 mv 或 cp 时，mv 或 cp 的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_fail`指定为 mv 或 cp 时需要填写 | `${EXEC_DIR}/fail` | | -tp | --timestamp\_precision | 时间戳精度
tsfile 非远程导入：-tp 指定 tsfile 文件的时间精度 手动校验和服务器的时间戳是否一致 不一致返回报错信息
远程导入：-tp 指定 tsfile 文件的时间精度 pipe 自动校验时间戳精度是否一致 不一致返回 pipe 报错信息 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms| diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Maintenance-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Maintenance-Tool_timecho.md index f31b5cfcf..14859a654 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Maintenance-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Maintenance-Tool_timecho.md @@ -172,7 +172,7 @@ IOTDB_JMX_OPTS="$IOTDB_JMX_OPTS -XX:MaxGCPauseMillis=200" | storage_tsdb_retention_time | 默认保存数据天数 默认15天 | 非必填 | | storage_tsdb_retention_size | 指定block可以保存的数据大小默认512M ，注意单位KB, MB, GB, TB, PB, EB | 非必填 | -如果在config/xxx.yaml的`iotdb-system.properties`和`iotdb-system.properties`中配置了metrics,则会自动把配置放入到promethues无需手动修改 +如果在config/xxx.yaml的`iotdb-system.properties`和`iotdb-system.properties`中配置了metrics,则会自动把配置放入到Prometheus无需手动修改 注意:如何配置yaml key对应的值包含特殊字符如:等建议整个value使用双引号，对应的文件路径中不要使用包含空格的路径，防止出现识别出现异常问题。 diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md index 1b8126809..1518d5c57 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_apache.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------------|----------------------------|-----------------------------------------------| ----------------------------------- |---------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md index 8dc2e3d89..c7affc309 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Export-Tool_timecho.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------------|--------------------------|-----------------------------------------------| ----------------------------------- |---------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6 版本之前为 root) | diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md index 7d8acf4d9..961a450eb 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_apache.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | --------------------- | ------------------------------- |------------------------------------------------| -------------- |-----------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md index 72bc81ca2..1b418708d 100644 --- a/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md +++ b/src/zh/UserGuide/latest-Table/Tools-System/Schema-Import-Tool_timecho.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------------|------------------------------|------------------------------------------------| -------------- |-------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6 版本之前为 root) | diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md index 7e1f4dd61..aab70b93e 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_apache.md @@ -83,22 +83,22 @@ - 树模型与表模型的`pipe`及`pipe plugins`在设计上相互隔离，建议在创建`pipe`前先通过`show`命令查询当前`-sql_dialect`参数配置下可用的内置插件，以确保语法兼容性和功能支持。 - 当 Pipe 向接收端写入数据因字段类型不匹配而失败时，IoTDB 可按照目标端已有 schema 的字段类型对数据进行转换，并重试写入，以提高同步成功率。该能力由 `sink.exception.data.convert-on-type-mismatch` 控制，参数说明见后文 sink 参数表。 - * 类型不匹配时的转换规则如下： - - | 源类型 | 目标类型 | 转换规则 | - | -------------------- | ----------- | -------------------------------------------------------------------------------- | - | 数值类型 | 数值类型 | 按目标数值类型进行转换，可能发生截断、精度损失或溢出。 | - | 数值类型 | BOOLEAN | `0`转换为`false`，非`0`转换为`true`。 | - | BOOLEAN | 数值类型 | `true`转换为`1`，`false`转换为`0`。 | - | TEXT、STRING、BLOB | BOOLEAN | 按字符串解析为 BOOLEAN。 | - | TEXT、STRING、BLOB | 数值类型 | 按字符串解析为目标数值类型；解析失败时写入默认值`0`、`0L`或`0.0`。 | - | TEXT、STRING、BLOB | TIMESTAMP | 按字符串解析为 TIMESTAMP；解析失败时写入默认值`0L`。 | - | TEXT、STRING、BLOB | DATE | 按字符串解析为 DATE；解析失败时写入默认日期`1970-01-01`。 | - | 非法数值 | DATE | 若无法转换为合法 DATE，则写入默认日期`1970-01-01`。 | - | DATE | TIMESTAMP | 按 UTC 转换为当天零点对应的时间戳。 | - | TIMESTAMP | DATE | 按 UTC 转换为对应日期。 | - - > 注意：自动转换基于目标端已有 schema 执行，不会自动修改目标端 schema；该能力优先保证同步继续进行，可能导致精度损失或默认值写入。 +类型不匹配时的转换规则如下： + +| 源类型 | 目标类型 | 转换规则 | +| -------------------- | ----------- | -------------------------------------------------------------------------------- | +| 数值类型 | 数值类型 | 按目标数值类型进行转换，可能发生截断、精度损失或溢出。 | +| 数值类型 | BOOLEAN | `0`转换为`false`，非`0`转换为`true`。 | +| BOOLEAN | 数值类型 | `true`转换为`1`，`false`转换为`0`。 | +| TEXT、STRING、BLOB | BOOLEAN | 按字符串解析为 BOOLEAN。 | +| TEXT、STRING、BLOB | 数值类型 | 按字符串解析为目标数值类型；解析失败时写入默认值`0`、`0L`或`0.0`。 | +| TEXT、STRING、BLOB | TIMESTAMP | 按字符串解析为 TIMESTAMP；解析失败时写入默认值`0L`。 | +| TEXT、STRING、BLOB | DATE | 按字符串解析为 DATE；解析失败时写入默认日期`1970-01-01`。 | +| 非法数值 | DATE | 若无法转换为合法 DATE，则写入默认日期`1970-01-01`。 | +| DATE | TIMESTAMP | 按 UTC 转换为当天零点对应的时间戳。 | +| TIMESTAMP | DATE | 按 UTC 转换为对应日期。 | + +> 注意：自动转换基于目标端已有 schema 执行，不会自动修改目标端 schema；该能力优先保证同步继续进行，可能导致精度损失或默认值写入。 ## 2. 使用说明 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md index e05d9c999..82de87d78 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Data-Sync_timecho.md @@ -84,22 +84,22 @@ - 自 V2.0.9.2 版本起支持 Object 类型数据导出。 - 当 Pipe 向接收端写入数据因字段类型不匹配而失败时，IoTDB 可按照目标端已有 schema 的字段类型对数据进行转换，并重试写入，以提高同步成功率。该能力由 `sink.exception.data.convert-on-type-mismatch` 控制，参数说明见后文 sink 参数表。 - * 类型不匹配时的转换规则如下： - - | 源类型 | 目标类型 | 转换规则 | - | -------------------- | ----------- | -------------------------------------------------------------------------------- | - | 数值类型 | 数值类型 | 按目标数值类型进行转换，可能发生截断、精度损失或溢出。 | - | 数值类型 | BOOLEAN | `0`转换为`false`，非`0`转换为`true`。 | - | BOOLEAN | 数值类型 | `true`转换为`1`，`false`转换为`0`。 | - | TEXT、STRING、BLOB | BOOLEAN | 按字符串解析为 BOOLEAN。 | - | TEXT、STRING、BLOB | 数值类型 | 按字符串解析为目标数值类型；解析失败时写入默认值`0`、`0L`或`0.0`。 | - | TEXT、STRING、BLOB | TIMESTAMP | 按字符串解析为 TIMESTAMP；解析失败时写入默认值`0L`。 | - | TEXT、STRING、BLOB | DATE | 按字符串解析为 DATE；解析失败时写入默认日期`1970-01-01`。 | - | 非法数值 | DATE | 若无法转换为合法 DATE，则写入默认日期`1970-01-01`。 | - | DATE | TIMESTAMP | 按 UTC 转换为当天零点对应的时间戳。 | - | TIMESTAMP | DATE | 按 UTC 转换为对应日期。 | - - > 注意：自动转换基于目标端已有 schema 执行，不会自动修改目标端 schema；该能力优先保证同步继续进行，可能导致精度损失或默认值写入。 +类型不匹配时的转换规则如下： + +| 源类型 | 目标类型 | 转换规则 | +| -------------------- | ----------- | -------------------------------------------------------------------------------- | +| 数值类型 | 数值类型 | 按目标数值类型进行转换，可能发生截断、精度损失或溢出。 | +| 数值类型 | BOOLEAN | `0`转换为`false`，非`0`转换为`true`。 | +| BOOLEAN | 数值类型 | `true`转换为`1`，`false`转换为`0`。 | +| TEXT、STRING、BLOB | BOOLEAN | 按字符串解析为 BOOLEAN。 | +| TEXT、STRING、BLOB | 数值类型 | 按字符串解析为目标数值类型；解析失败时写入默认值`0`、`0L`或`0.0`。 | +| TEXT、STRING、BLOB | TIMESTAMP | 按字符串解析为 TIMESTAMP；解析失败时写入默认值`0L`。 | +| TEXT、STRING、BLOB | DATE | 按字符串解析为 DATE；解析失败时写入默认日期`1970-01-01`。 | +| 非法数值 | DATE | 若无法转换为合法 DATE，则写入默认日期`1970-01-01`。 | +| DATE | TIMESTAMP | 按 UTC 转换为当天零点对应的时间戳。 | +| TIMESTAMP | DATE | 按 UTC 转换为对应日期。 | + +> 注意：自动转换基于目标端已有 schema 执行，不会自动修改目标端 schema；该能力优先保证同步继续进行，可能导致精度损失或默认值写入。 ## 2. 使用说明 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md index 6f4005271..5cefc4833 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_apache.md @@ -558,7 +558,7 @@ show configuration on 1 with desc; +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | name| value| default_value| description| +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| cluster_name| defaultCluster| defaultCluster| Used for indicate cluster name and distinguish different cluster. If you need to modify the cluster name, it's recommended to use 'set configuration "cluster_name=xxx"' sql. Manually modifying configuration file is not recommended, which may cause node restart fail.effectiveMode: hot_reload.Datatype: string| +| cluster_name| defaultCluster| defaultCluster| 用于标识集群名称并区分不同集群。如果需要修改集群名称，建议使用 SQL 语句 'set configuration "cluster_name=xxx"'。不建议手动修改配置文件，否则可能导致节点重启失败。effectiveMode: hot_reload。Datatype: string| | cn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710|For the first ConfigNode to start, cn_seed_config_node points to its own cn_internal_address:cn_internal_port. For other ConfigNodes that to join the cluster, cn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this ConfigNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | dn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710| dn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this DataNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | cn_internal_address| 127.0.0.1| 127.0.0.1| Used for RPC communication inside cluster. Could set 127.0.0.1(for local test) or ipv4 address.effectiveMode: first_start.Datatype: String| diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md index 06cd46b1f..20d67a00e 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Maintenance-statement_timecho.md @@ -591,7 +591,7 @@ show configuration on 1 with desc; +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | name| value| default_value| description| +--------------------------------------+-----------------------------------------------------------------+-----------------------------------------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ -| cluster_name| defaultCluster| defaultCluster| Used for indicate cluster name and distinguish different cluster. If you need to modify the cluster name, it's recommended to use 'set configuration "cluster_name=xxx"' sql. Manually modifying configuration file is not recommended, which may cause node restart fail.effectiveMode: hot_reload.Datatype: string| +| cluster_name| defaultCluster| defaultCluster| 用于标识集群名称并区分不同集群。如果需要修改集群名称，建议使用 SQL 语句 'set configuration "cluster_name=xxx"'。不建议手动修改配置文件，否则可能导致节点重启失败。effectiveMode: hot_reload。Datatype: string| | cn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710|For the first ConfigNode to start, cn_seed_config_node points to its own cn_internal_address:cn_internal_port. For other ConfigNodes that to join the cluster, cn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this ConfigNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | dn_seed_config_node| 127.0.0.1:10710| 127.0.0.1:10710| dn_seed_config_node points to any running ConfigNode's cn_internal_address:cn_internal_port. Note: After this DataNode successfully joins the cluster for the first time, this parameter is no longer used. Each node automatically maintains the list of ConfigNodes and traverses connections when restarting. Format: address:port e.g. 127.0.0.1:10710.effectiveMode: first_start.Datatype: String| | cn_internal_address| 127.0.0.1| 127.0.0.1| Used for RPC communication inside cluster. Could set 127.0.0.1(for local test) or ipv4 address.effectiveMode: first_start.Datatype: String| diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md index 12537de93..a0a6e0242 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Pattern-Query_timecho.md @@ -231,7 +231,7 @@ MATCH_RECOGNIZE ( | ------------------------------------------------------------- | --------------------------------------------------- | ------------------------ | | `AFTER MATCH SKIP PAST LAST ROW` | 默认行为。在当前匹配的最后一行之后的下一行开始。 | 否 | | `AFTER MATCH SKIP TO NEXT ROW` | 在当前匹配中的第二行开始。 | 是 | -| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | 跳转到某个模式变量的 [ 第一行 | 最后一行 ] 开始。 | 是 | +| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | 跳转到某个模式变量的 [ 第一行 \| 最后一行 ] 开始。 | 是 | * 在所有可能的配置中，仅当 `ALL ROWS PER MATCH WITH UNMATCHED ROWS` 与 `AFTER MATCH SKIP PAST LAST ROW` 联合使用时，系统才能确保对每个输入行恰好生成一条输出记录。 diff --git a/src/zh/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md b/src/zh/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md index 003fdcedb..a62e9bc39 100644 --- a/src/zh/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md +++ b/src/zh/UserGuide/latest-Table/User-Manual/Timeseries-Featured-Analysis_timecho.md @@ -233,7 +233,7 @@ MATCH_RECOGNIZE ( | ------------------------------------------------------------- | --------------------------------------------------- | ------------------------ | | `AFTER MATCH SKIP PAST LAST ROW` | 默认行为。在当前匹配的最后一行之后的下一行开始。 | 否 | | `AFTER MATCH SKIP TO NEXT ROW` | 在当前匹配中的第二行开始。 | 是 | -| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | 跳转到某个模式变量的 [ 第一行 | 最后一行 ] 开始。 | 是 | +| `AFTER MATCH SKIP TO [ FIRST \| LAST ] pattern_variable` | 跳转到某个模式变量的 [ 第一行 \| 最后一行 ] 开始。 | 是 | * 在所有可能的配置中，仅当 `ALL ROWS PER MATCH WITH UNMATCHED ROWS` 与 `AFTER MATCH SKIP PAST LAST ROW` 联合使用时，系统才能确保对每个输入行恰好生成一条输出记录。 diff --git a/src/zh/UserGuide/latest/AI-capability/AINode_apache.md b/src/zh/UserGuide/latest/AI-capability/AINode_apache.md index c9ec4c493..979a199e2 100644 --- a/src/zh/UserGuide/latest/AI-capability/AINode_apache.md +++ b/src/zh/UserGuide/latest/AI-capability/AINode_apache.md @@ -98,23 +98,23 @@ SQL中参数的具体含义如下： - 模型配置文件：模型注册时需要提供的与模型结构有关的参数，其中必须包含模型的输入输出维度用于模型推理： - - | **参数名** | **参数描述** | **示例** | - | ------------ | ---------------------------- | -------- | - | input_shape | 模型输入的行列，用于模型推理 | [96,2] | - | output_shape | 模型输出的行列，用于模型推理 | [48,2] | + | **参数名** | **参数描述** | **示例** | + | ------------ | ---------------------------- | -------- | + | input_shape | 模型输入的行列，用于模型推理 | [96,2] | + | output_shape | 模型输出的行列，用于模型推理 | [48,2] | - - ​ 除了模型推理外，还可以指定模型输入输出的数据类型： + 除了模型推理外，还可以指定模型输入输出的数据类型： - - | **参数名** | **参数描述** | **示例** | - | ----------- | ------------------ | --------------------- | - | input_type | 模型输入的数据类型 | ['float32','float32'] | - | output_type | 模型输出的数据类型 | ['float32','float32'] | + | **参数名** | **参数描述** | **示例** | + | ----------- | ------------------ | --------------------- | + | input_type | 模型输入的数据类型 | ['float32','float32'] | + | output_type | 模型输出的数据类型 | ['float32','float32'] | - - ​ 除此之外，可以额外指定备注信息用于在模型管理时进行展示 + 除此之外，可以额外指定备注信息用于在模型管理时进行展示 - - | **参数名** | **参数描述** | **示例** | - | ---------- | ---------------------------------------------- | ------------------------------------------- | - | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | + | **参数名** | **参数描述** | **示例** | + | ---------- | ---------------------------------------------- | ------------------------------------------- | + | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | 除了本地模型文件的注册，还可以通过URI来指定远程资源路径来进行注册，使用开源的模型仓库（例如HuggingFace）。 @@ -599,4 +599,4 @@ Total line number = 144 ![](/img/s6.png) -可以看到，Stray模型对输入序列变化进行了建模，成功检测出出现异常的时间点。 \ No newline at end of file +可以看到，Stray模型对输入序列变化进行了建模，成功检测出出现异常的时间点。 diff --git a/src/zh/UserGuide/latest/AI-capability/AINode_timecho.md b/src/zh/UserGuide/latest/AI-capability/AINode_timecho.md index c551a0b0c..22e29542e 100644 --- a/src/zh/UserGuide/latest/AI-capability/AINode_timecho.md +++ b/src/zh/UserGuide/latest/AI-capability/AINode_timecho.md @@ -98,23 +98,23 @@ SQL中参数的具体含义如下： - 模型配置文件：模型注册时需要提供的与模型结构有关的参数，其中必须包含模型的输入输出维度用于模型推理： - - | **参数名** | **参数描述** | **示例** | - | ------------ | ---------------------------- | -------- | - | input_shape | 模型输入的行列，用于模型推理 | [96,2] | - | output_shape | 模型输出的行列，用于模型推理 | [48,2] | + | **参数名** | **参数描述** | **示例** | + | ------------ | ---------------------------- | -------- | + | input_shape | 模型输入的行列，用于模型推理 | [96,2] | + | output_shape | 模型输出的行列，用于模型推理 | [48,2] | - - ​ 除了模型推理外，还可以指定模型输入输出的数据类型： + 除了模型推理外，还可以指定模型输入输出的数据类型： - - | **参数名** | **参数描述** | **示例** | - | ----------- | ------------------ | --------------------- | - | input_type | 模型输入的数据类型 | ['float32','float32'] | - | output_type | 模型输出的数据类型 | ['float32','float32'] | + | **参数名** | **参数描述** | **示例** | + | ----------- | ------------------ | --------------------- | + | input_type | 模型输入的数据类型 | ['float32','float32'] | + | output_type | 模型输出的数据类型 | ['float32','float32'] | - - ​ 除此之外，可以额外指定备注信息用于在模型管理时进行展示 + 除此之外，可以额外指定备注信息用于在模型管理时进行展示 - - | **参数名** | **参数描述** | **示例** | - | ---------- | ---------------------------------------------- | ------------------------------------------- | - | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | + | **参数名** | **参数描述** | **示例** | + | ---------- | ---------------------------------------------- | ------------------------------------------- | + | attributes | 可选，用户自行设定的模型备注信息，用于模型展示 | 'model_type': 'dlinear','kernel_size': '25' | 除了本地模型文件的注册，还可以通过URI来指定远程资源路径来进行注册，使用开源的模型仓库（例如HuggingFace）。 @@ -665,4 +665,4 @@ Total line number = 144 ![](/img/s6.png) -可以看到，Stray模型对输入序列变化进行了建模，成功检测出出现异常的时间点。 \ No newline at end of file +可以看到，Stray模型对输入序列变化进行了建模，成功检测出出现异常的时间点。 diff --git a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md index e1af1e1d0..99712b134 100644 --- a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md +++ b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_apache.md @@ -148,7 +148,7 @@ IoTDB> show models ### 附录 -**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) +**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) **[2]** TIMER-XL- LONG-CONTEXT TRANSFORMERS FOR UNIFIED TIME SERIES FORECASTING ,Yong Liu, Guo Qin, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref2) diff --git a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md index 3d86bfc4f..953b3ed9a 100644 --- a/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest/AI-capability/TimeSeries-Large-Model_Upgrade_timecho.md @@ -148,7 +148,7 @@ IoTDB> show models ### 附录 -**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) +**[1]** Timer- Generative Pre-trained Transformers Are Large Time Series Models, Yong Liu, Haoran Zhang, Chenyu Li, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref1) **[2]** TIMER-XL- LONG-CONTEXT TRANSFORMERS FOR UNIFIED TIME SERIES FORECASTING ,Yong Liu, Guo Qin, Xiangdong Huang, Jianmin Wang, Mingsheng Long. [↩ 返回](#ref2) diff --git a/src/zh/UserGuide/latest/Basic-Concept/Query-Data_apache.md b/src/zh/UserGuide/latest/Basic-Concept/Query-Data_apache.md index d6d283269..2ef579857 100644 --- a/src/zh/UserGuide/latest/Basic-Concept/Query-Data_apache.md +++ b/src/zh/UserGuide/latest/Basic-Concept/Query-Data_apache.md @@ -3010,7 +3010,7 @@ select s1, s2 into root.sg_copy.d1(t1, t2), aligned root.sg_copy.d2(t1, t2) from #### 实现 IoTDB 内部 ETL 对原始数据进行 ETL 处理后写入新序列。 ```sql -SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEIVCE; +SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEVICE; ``` ```shell +--------------+-------------------+---------------------------+--------+ diff --git a/src/zh/UserGuide/latest/Basic-Concept/Query-Data_timecho.md b/src/zh/UserGuide/latest/Basic-Concept/Query-Data_timecho.md index f367c3294..5f2dd6c68 100644 --- a/src/zh/UserGuide/latest/Basic-Concept/Query-Data_timecho.md +++ b/src/zh/UserGuide/latest/Basic-Concept/Query-Data_timecho.md @@ -3010,7 +3010,7 @@ select s1, s2 into root.sg_copy.d1(t1, t2), aligned root.sg_copy.d2(t1, t2) from #### 实现 IoTDB 内部 ETL 对原始数据进行 ETL 处理后写入新序列。 ```sql -SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEIVCE; +SELECT preprocess_udf(s1, s2) INTO ::(preprocessed_s1, preprocessed_s2) FROM root.sg.* ALIGN BY DEVICE; ``` ```shell +--------------+-------------------+---------------------------+--------+ diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md index adb5f6979..e57726491 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_apache.md @@ -231,7 +231,7 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_apache.md)中同步。可联系商业支持获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.5】小节。 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md index dfff7a9a0..ae67e19e3 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_Upgrade_timecho.md @@ -263,6 +263,6 @@ IoTDB> show cluster * 备份 conf 目录下已修改的配置文件，然后替换 conf 文件夹，并将修改的配置同步到对应位置 3. 更新内置模型权重（可选） - * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history\_timecho.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 + * 若新版本涉及内置模型更新，相关信息将在[发布历史](../IoTDB-Introduction/Release-history_timecho.md)中同步。可联系天谋工作人员获取最新权重包，并将权重包替换至 `data/ainode/models/builtin` 目录 4. 升级完毕后，可启动 AINode 服务，并查看节点状态，具体命令可参考【3.4】和【3.6】小节。 diff --git a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md index 6e816560e..ed5592f04 100644 --- a/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md +++ b/src/zh/UserGuide/latest/Deployment-and-Maintenance/AINode_Deployment_apache.md @@ -51,7 +51,7 @@ AINode 安装包（`apache-iotdb--ainode-bin.zip`），安装包解压 | README_ZH.md | 文件 | markdown格式的中文版说明 | | README.md | 文件 | 使用说明 | -### 2.1 前置检查 +### 2.2 前置检查 为确保您获取的 AINode 安装包完整且正确，在执行安装部署前建议您进行SHA512校验。 @@ -253,4 +253,4 @@ cd Python-3.10.0 make sudo make install python3 --version -``` \ No newline at end of file +``` diff --git a/src/zh/UserGuide/latest/SQL-Manual/Function-and-Expression.md b/src/zh/UserGuide/latest/SQL-Manual/Function-and-Expression.md index 4bfa2c8f4..43eaea52c 100644 --- a/src/zh/UserGuide/latest/SQL-Manual/Function-and-Expression.md +++ b/src/zh/UserGuide/latest/SQL-Manual/Function-and-Expression.md @@ -872,7 +872,7 @@ select a, a in (1, 2) from root.test; | 函数名 | 可接收的输入序列类型 | 必要的属性参数 | 输出序列类型 | 功能类型 | |----------|--------------------------------|---------------------------------------|------------|--------------------------------------------------| | ON_OFF | INT32 / INT64 / FLOAT / DOUBLE | `threshold`:DOUBLE类型 | BOOLEAN 类型 | 返回`ts_value >= threshold`的bool值 | -| IN_RANGE | INT32 / INT64 / FLOAT / DOUBLE | `lower`:DOUBLE类型
`upper`:DOUBLE类型 | BOOLEAN类型 | 返回`ts_value >= lower && ts_value <= upper`的bool值 | | +| IN_RANGE | INT32 / INT64 / FLOAT / DOUBLE | `lower`:DOUBLE类型
`upper`:DOUBLE类型 | BOOLEAN类型 | 返回`ts_value >= lower && ts_value <= upper`的bool值 | 测试数据： @@ -2143,9 +2143,9 @@ It costs 0.006s | 函数名 | 输入序列类型 | 属性参数 | 输出序列类型 | 功能描述 | |-------------------|--------------------------------------|------------------------------------------------|-------|------------------------------------------------------------------| | ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | -| NON_ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | | -| ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | | -| NON_ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | | +| NON_ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | +| ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | +| NON_ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | 测试数据: ``` @@ -3097,4 +3097,4 @@ from root.test4 |1970-01-01T08:00:00.003+08:00| 3.0| 3.299999952316284| |1970-01-01T08:00:00.004+08:00| 4.0| 4.44444465637207| +-----------------------------+------------+-------------------+ -``` \ No newline at end of file +``` diff --git a/src/zh/UserGuide/latest/SQL-Manual/Operator-and-Expression.md b/src/zh/UserGuide/latest/SQL-Manual/Operator-and-Expression.md index aa026b9b0..4820b213a 100644 --- a/src/zh/UserGuide/latest/SQL-Manual/Operator-and-Expression.md +++ b/src/zh/UserGuide/latest/SQL-Manual/Operator-and-Expression.md @@ -145,7 +145,7 @@ OR, |, || | 函数名 | 可接收的输入序列类型 | 必要的属性参数 | 输出序列类型 | 功能类型 | |----------|--------------------------------|---------------------------------------|------------|--------------------------------------------------| | ON_OFF | INT32 / INT64 / FLOAT / DOUBLE | `threshold`:DOUBLE | BOOLEAN | 返回`ts_value >= threshold`的bool值 | -| IN_RANGE | INT32 / INT64 / FLOAT / DOUBLE | `lower`:DOUBLE
`upper`:DOUBLE | BOOLEAN | 返回`ts_value >= lower && ts_value <= upper`的bool值 | | +| IN_RANGE | INT32 / INT64 / FLOAT / DOUBLE | `lower`:DOUBLE
`upper`:DOUBLE | BOOLEAN | 返回`ts_value >= lower && ts_value <= upper`的bool值 | 详细说明及示例见文档 [比较运算符和函数](../SQL-Manual/Function-and-Expression.md#_3-比较运算符和函数)。 @@ -201,9 +201,9 @@ OR, |, || | 函数名 | 输入序列类型 | 属性参数 | 输出序列类型 | 功能描述 | |-------------------|--------------------------------------|------------------------------------------------|-------|------------------------------------------------------------------| | ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | -| NON_ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | | -| ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | | -| NON_ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | | +| NON_ZERO_DURATION | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值0
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与持续时间，持续时间t(单位ms)满足`t >= min && t <= max` | +| ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | +| NON_ZERO_COUNT | INT32/ INT64/ FLOAT/ DOUBLE/ BOOLEAN | `min`:可选，默认值1
`max`:可选，默认值`Long.MAX_VALUE` | Long | 返回时间序列连续不为0(false)的开始时间与其后数据点的个数，数据点个数n满足`n >= min && n <= max` | 详细说明及示例见文档 [区间查询函数](../SQL-Manual/Function-and-Expression.md#_9-区间查询函数)。 diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md index d03cac9c9..d6145c308 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_apache.md @@ -34,7 +34,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------|-------------------------|----------------------------------------------------| -------------- |---------------------------------------------------------------------------| | -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md index 329dc0814..2bdbee362 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Export-Tool_timecho.md @@ -34,7 +34,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | -------- |-------------------------| ---------------------------------------------------------------------- | -------------- |------------------------------------------| | -ft | --file\_type | 导出文件的类型，可以选择：csv、sql、tsfile | √ | | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6.x 版本之前为 root) | diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_apache.md index 8f3ce6876..4bfe06621 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_apache.md @@ -43,15 +43,15 @@ IoTDB 支持三种方式进行数据导入： | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | ---------- |---------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| -------------- |---------------------------| -| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | -| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为csv sql tsfile这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | +| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为csv sql tsfile这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | | | -tn | --thread\_num | 最大并行线程数 | 否 | 8
范围：0～Integer.Max=2147483647 | | -tz | --timezone | 时区设置，例如`+08:00`或`-01:00` | 否 | 本机系统时间 | -| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | +| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | | | -usessl | --use_ssl | 使用 SSL 协议，自 V2.0.9-beta 起支持 | 否 | - | | -ts | --trust_store | 信任库。支持隐藏输入，自 V2.0.9-beta 起支持 | 否 | - | | -tpw | --trust_store_password | 信任库密码。支持隐藏输入，自 V2.0.9-beta 起支持 | 否 | - | @@ -91,8 +91,7 @@ IoTDB 支持三种方式进行数据导入： | -aligned | --use\_aligned | 是否导入为对齐序列 | 否 | false | | -batch | --batch\_size | 指定每调用一次接口处理的数据行数（最小值为1，最大值为Integer.​*MAX\_VALUE*​） | 否 | 100000
范围：0～Integer.Max=2147483647 | | -ti | --type\_infer | 通过选项定义类型信息，例如`"boolean=text,int=long, ..."` | 否 | 无 | -| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms -| +| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms | #### 2.2.3 运行示例 @@ -227,7 +226,7 @@ error: Invalid thread number '0'. Please set a positive integer. | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | ---------- | ------------------------ |----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -------------------- | | -os| --on\_succcess| 1. none：不删除
2. mv：移动成功的文件到目标文件夹
3. cp：硬连接（拷贝）成功的文件到目标文件夹
4. delete：删除 | √ || -| -sd | --success\_dir | 当`--on_succcess`为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_succcess`为mv或cp时需要填写 | `${EXEC_DIR}/success`| +| -sd | --success\_dir | 当`--on_success`为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_success`为mv或cp时需要填写 | `${EXEC_DIR}/success`| | -of| --on\_fail| 1. none：跳过
2. mv：移动失败的文件到目标文件夹
3. cp：硬连接（拷贝）失败的文件到目标文件夹
4. delete：删除 | √ || | -fd | --fail\_dir | 当`--on_fail`指定为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_fail`指定为mv或cp时需要填写 | `${EXEC_DIR}/fail` | | -tp | --timestamp\_precision | 时间戳精度
tsfile非远程导入：-tp 指定tsfile文件的时间精度 手动校验和服务器的时间戳是否一致 不一致返回报错信息
远程导入：-tp 指定tsfile文件的时间精度 pipe自动校验时间戳精度是否一致 不一致返回pipe报错信息 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms| @@ -324,4 +323,4 @@ IoTDB> select * from root.testdb.** +-----------------------------+------------------------------------+---------------------------------+-------------------------------+ |2025-04-17T10:35:47.218+08:00| 22.3| 19.4| true| +-----------------------------+------------------------------------+---------------------------------+-------------------------------+ -``` \ No newline at end of file +``` diff --git a/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_timecho.md index aed95c563..236dac53b 100644 --- a/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Data-Import-Tool_timecho.md @@ -43,15 +43,15 @@ IoTDB 支持三种方式进行数据导入： | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------|---------------------------|-----------------------------------------------------------------------------------------------------------------------------| -------------- |--------------------------------------| -| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | -| -h | -- host | 主机名 | 否 | 127.0.0.1 | +| -ft | --file\_type | 导入文件的类型，可以选择：csv、sql、tsfile | √ | | +| -h | --host | 主机名 | 否 | 127.0.0.1 | | -p | --port | 端口号 | 否 | 6667 | | -u | --username | 用户名 | 否 | root | | -pw | --password | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6.x 版本之前为 root) | -| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为csv sql tsfile这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | +| -s | --source | 待加载的脚本文件(夹)的本地目录路径
如果为csv sql tsfile这三个支持的格式，直接导入
不支持的格式，报错提示`The file name must end with "csv" or "sql"or "tsfile"!` | √ | | | -tn | --thread\_num | 最大并行线程数 | 否 | 8
范围：0～Integer.Max=2147483647 | | -tz | --timezone | 时区设置，例如`+08:00`或`-01:00` | 否 | 本机系统时间 | -| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | +| -help | --help | 显示帮助信息,支持分开展示和全部展示`-help`或`-help csv` | 否 | | | -usessl | --use_ssl | 使用 SSL 协议，自 V2.0.9.1 起支持 | 否 | - | | -ts | --trust_store | 信任库。支持隐藏输入，自 V2.0.9.1 起支持 | 否 | - | | -tpw | --trust_store_password | 信任库密码。支持隐藏输入，自 V2.0.9.1 起支持 | 否 | - | @@ -91,8 +91,7 @@ IoTDB 支持三种方式进行数据导入： | -aligned | --use\_aligned | 是否导入为对齐序列 | 否 | false | | -batch | --batch\_size | 指定每调用一次接口处理的数据行数（最小值为1，最大值为Integer.​*MAX\_VALUE*​） | 否 | 100000
范围：0～Integer.Max=2147483647 | | -ti | --type\_infer | 通过选项定义类型信息，例如`"boolean=text,int=long, ..."` | 否 | 无 | -| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms -| +| -tp | --timestamp\_precision | 时间戳精度 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms | #### 2.2.3 运行示例 @@ -231,7 +230,7 @@ error: Invalid thread number '0'. Please set a positive integer. | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | ---------- | ------------------------ |----------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------| -------------------- | | -os| --on\_succcess| 1. none：不删除
2. mv：移动成功的文件到目标文件夹
3. cp：硬连接（拷贝）成功的文件到目标文件夹
4. delete：删除 | √ || -| -sd | --success\_dir | 当`--on_succcess`为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_succcess`为mv或cp时需要填写 | `${EXEC_DIR}/success`| +| -sd | --success\_dir | 当`--on_success`为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_success`为mv或cp时需要填写 | `${EXEC_DIR}/success`| | -of| --on\_fail| 1. none：跳过
2. mv：移动失败的文件到目标文件夹
3. cp：硬连接（拷贝）失败的文件到目标文件夹
4. delete：删除 | √ || | -fd | --fail\_dir | 当`--on_fail`指定为mv或cp时，mv或cp的目标文件夹。文件的文件名变为文件夹打平后拼接原有文件名 | 当`--on_fail`指定为mv或cp时需要填写 | `${EXEC_DIR}/fail` | | -tp | --timestamp\_precision | 时间戳精度
tsfile非远程导入：-tp 指定tsfile文件的时间精度 手动校验和服务器的时间戳是否一致 不一致返回报错信息
远程导入：-tp 指定tsfile文件的时间精度 pipe自动校验时间戳精度是否一致 不一致返回pipe报错信息 | 否：
1. ms（毫秒）
2. us（微秒）
3. ns（纳秒） | ms| @@ -330,4 +329,4 @@ IoTDB> select * from root.testdb.** +-----------------------------+------------------------------------+---------------------------------+-------------------------------+ |2025-04-17T10:35:47.218+08:00| 22.3| 19.4| true| +-----------------------------+------------------------------------+---------------------------------+-------------------------------+ -``` \ No newline at end of file +``` diff --git a/src/zh/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md index 1457e848a..c462adde3 100644 --- a/src/zh/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Maintenance-Tool_timecho.md @@ -172,7 +172,7 @@ IOTDB_JMX_OPTS="$IOTDB_JMX_OPTS -XX:MaxGCPauseMillis=200" | storage\_tsdb\_retention\_time | 默认保存数据天数 默认15天 | 非必填 | | storage\_tsdb\_retention\_size | 指定block可以保存的数据大小默认512M ，注意单位KB, MB, GB, TB, PB, EB | 非必填 | -如果在config/xxx.yaml的`iotdb-system.properties`和`iotdb-system.properties`中配置了metrics,则会自动把配置放入到promethues无需手动修改 +如果在config/xxx.yaml的`iotdb-system.properties`和`iotdb-system.properties`中配置了metrics,则会自动把配置放入到Prometheus无需手动修改 注意:如何配置yaml key对应的值包含特殊字符如:等建议整个value使用双引号，对应的文件路径中不要使用包含空格的路径，防止出现识别出现异常问题。 diff --git a/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md index 3fdc7ddcc..614207c47 100644 --- a/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_apache.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | --------------------- |---------------------------| ------------------------------------------------------------------------ | ----------------------------------- |---------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md index c7e544003..ffb239ea3 100644 --- a/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Schema-Export-Tool_timecho.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | --------------------- | -------------------------- | ------------------------------------------------------------------------ | ----------------------------------- |---------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6.x 版本之前为 root) | diff --git a/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md b/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md index c7761bf26..2939967db 100644 --- a/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md +++ b/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_apache.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | | --------------------- |-----------------------------| ----------------------------------------------------------------------------- | -------------- |-----------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9-beta 起支持隐藏输入 | 否 | root | diff --git a/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md b/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md index e60f962b8..6b5ab5743 100644 --- a/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md +++ b/src/zh/UserGuide/latest/Tools-System/Schema-Import-Tool_timecho.md @@ -31,7 +31,7 @@ | 参数缩写 | 参数全称 | 参数含义 | 是否为必填项 | 默认值 | |----------------|--------------------------------|----------------------------------------------|--------|--------------------------------------| -| `-h` | `-- host` | 主机名 | 否 | 127.0.0.1 | +| `-h` | `--host` | 主机名 | 否 | 127.0.0.1 | | `-p` | `--port` | 端口号 | 否 | 6667 | | `-u` | `--username` | 用户名 | 否 | root | | `-pw` | `--password` | 密码，自 V2.0.9.1 起支持隐藏输入 | 否 | TimechoDB@2021 (V2.0.6.x 版本之前为 root) | diff --git a/src/zh/UserGuide/latest/User-Manual/IoTDB-View_timecho.md b/src/zh/UserGuide/latest/User-Manual/IoTDB-View_timecho.md index 6d86293d2..c3fa738ee 100644 --- a/src/zh/UserGuide/latest/User-Manual/IoTDB-View_timecho.md +++ b/src/zh/UserGuide/latest/User-Manual/IoTDB-View_timecho.md @@ -308,7 +308,7 @@ AS SELECT temperature FROM root.db.* ``` -这里仿照了查询写回（`SELECT INTO`）对命名规则的约定，使用变量占位符来指定命名规则。可以参考：[查询写回（SELECT INTO）](../Basic-Concept/Query-Data_timecho#查询写回（INTO-子句）) +这里仿照了查询写回（`SELECT INTO`）对命名规则的约定，使用变量占位符来指定命名规则。可以参考：[查询写回（SELECT INTO）](../Basic-Concept/Query-Data_timecho.md#_10-查询写回-into-子句) 这里`root.db.*.temperature`指定了有哪些时间序列会被包含在视图中；`${2}`则指定了从时间序列中的哪个节点提取出名字来命名序列视图。 @@ -544,4 +544,4 @@ AS #### Q4：是否支持序列视图重命名？ -> A：当前版本不支持重命名，可以自行创建新名称的视图投入使用。 \ No newline at end of file +> A：当前版本不支持重命名，可以自行创建新名称的视图投入使用。 diff --git a/src/zh/UserGuide/latest/User-Manual/User-defined-function_apache.md b/src/zh/UserGuide/latest/User-Manual/User-defined-function_apache.md index 0ba4f1ba5..5a5d1c2f3 100644 --- a/src/zh/UserGuide/latest/User-Manual/User-defined-function_apache.md +++ b/src/zh/UserGuide/latest/User-Manual/User-defined-function_apache.md @@ -458,7 +458,7 @@ public class Adder implements UDTF { 该方法每次处理原始数据的多行，经过性能测试，我们发现一次性处理多行的 UDTF 比一次处理一行的 UDTF 性能更好。原始数据由`Column[]`读入，由`ColumnBuilder`输出。您必须在一次`transform`方法调用中，根据每个输入的数据点输出一个对应的数据点，即输入和输出依然是一对一的。需要注意的是，输出数据点的类型必须与您在`beforeStart`方法中设置的一致，而输出数据点的时间戳必须是严格单调递增的。 -下面是一个实现了`void transform(Column[] columns, ColumnBuilder builder) throws Exceptionn`方法的完整 UDF 示例。它是一个加法器，接收两列时间序列输入，输出这两个数据点的代数和。 +下面是一个实现了`void transform(Column[] columns, ColumnBuilder builder) throws Exception`方法的完整 UDF 示例。它是一个加法器，接收两列时间序列输入，输出这两个数据点的代数和。 ``` java import org.apache.iotdb.tsfile.read.common.block.column.Column; diff --git a/src/zh/UserGuide/latest/User-Manual/User-defined-function_timecho.md b/src/zh/UserGuide/latest/User-Manual/User-defined-function_timecho.md index 35a998b90..9ae75d8b5 100644 --- a/src/zh/UserGuide/latest/User-Manual/User-defined-function_timecho.md +++ b/src/zh/UserGuide/latest/User-Manual/User-defined-function_timecho.md @@ -458,7 +458,7 @@ public class Adder implements UDTF { 该方法每次处理原始数据的多行，经过性能测试，我们发现一次性处理多行的 UDTF 比一次处理一行的 UDTF 性能更好。原始数据由`Column[]`读入，由`ColumnBuilder`输出。您必须在一次`transform`方法调用中，根据每个输入的数据点输出一个对应的数据点，即输入和输出依然是一对一的。需要注意的是，输出数据点的类型必须与您在`beforeStart`方法中设置的一致，而输出数据点的时间戳必须是严格单调递增的。 -下面是一个实现了`void transform(Column[] columns, ColumnBuilder builder) throws Exceptionn`方法的完整 UDF 示例。它是一个加法器，接收两列时间序列输入，输出这两个数据点的代数和。 +下面是一个实现了`void transform(Column[] columns, ColumnBuilder builder) throws Exception`方法的完整 UDF 示例。它是一个加法器，接收两列时间序列输入，输出这两个数据点的代数和。 ``` java import org.apache.iotdb.tsfile.read.common.block.column.Column;