Skip to content

Commit d10aa47

Browse files
leto-bleto-b
authored
fix sql dialect in common concepts and the link of zeppin in 1.3.x (#854)
1 parent 8c0fad1 commit d10aa47

File tree

10 files changed

+62
-62
lines changed

10 files changed

+62
-62
lines changed

‎src/.vuepress/sidebar/V1.3.x/zh.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -215,7 +215,7 @@ export const zhSidebar = {
215215
text: '可视化分析',
216216
collapsible: true,
217217
children: [
218-
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB' },
218+
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB_apache' },
219219
{ text: 'Grafana', link: 'Grafana-Connector' },
220220
{ text: 'Grafana插件', link: 'Grafana-Plugin' },
221221
{ text: 'DataEase', link: 'DataEase' },

‎src/.vuepress/sidebar_timecho/V1.3.x/zh.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -226,7 +226,7 @@ export const zhSidebar = {
226226
text: '可视化分析',
227227
collapsible: true,
228228
children: [
229-
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB' },
229+
{ text: 'Apache Zeppelin', link: 'Zeppelin-IoTDB_timecho' },
230230
{ text: 'Grafana', link: 'Grafana-Connector' },
231231
{ text: 'Grafana插件', link: 'Grafana-Plugin' },
232232
{ text: 'DataEase', link: 'DataEase' },

‎src/UserGuide/V1.3.x/Background-knowledge/Cluster-Concept_apache.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@
2323

2424
## Sql_dialect Related Concepts
2525

26-
| Concept | Meaning |
27-
| ----------------------- | ------------------------------------------------------------ |
28-
| sql_dialect | IoTDB supports two time-series data models (SQL dialects), both managing devices and measurement points. Tree: Manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. Table: Manages data in a relational table manner, where one table corresponds to a category of devices. |
29-
| Schema | Schema is the data model information of the database, i.e., tree structure or table structure. It includes definitions such as the names and data types of measurement points. |
30-
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
26+
| Concept | Meaning |
27+
| ----------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
28+
| sql_dialect | Tree model: manages devices and measurement points, manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. |
29+
| Schema | Schema is the data model information of the database, i.e., tree structure. It includes definitions such as the names and data types of measurement points. |
30+
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
3131
| Timeseries | Also known as: physical quantity, time series, timeline, point location, semaphore, indicator, measurement value, etc. It is a time series formed by arranging multiple data points in ascending order of timestamps. Usually, a Timeseries represents a collection point that can periodically collect physical quantities of the environment it is in. |
32-
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33-
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
32+
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33+
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
3434

3535
## Distributed Related Concepts
3636

‎src/UserGuide/V1.3.x/Background-knowledge/Cluster-Concept_timecho.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@
2323

2424
## Sql_dialect Related Concepts
2525

26-
| Concept | Meaning |
27-
| ----------------------- | ------------------------------------------------------------ |
28-
| sql_dialect | IoTDB supports two time-series data models (SQL dialects), both managing devices and measurement points. Tree: Manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. Table: Manages data in a relational table manner, where one table corresponds to a category of devices. |
29-
| Schema | Schema is the data model information of the database, i.e., tree structure or table structure. It includes definitions such as the names and data types of measurement points. |
30-
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
26+
| Concept | Meaning |
27+
| ----------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
28+
| sql_dialect | Tree model: manages devices and measurement points, manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. |
29+
| Schema | Schema is the data model information of the database, i.e., tree structure. It includes definitions such as the names and data types of measurement points. |
30+
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
3131
| Timeseries | Also known as: physical quantity, time series, timeline, point location, semaphore, indicator, measurement value, etc. It is a time series formed by arranging multiple data points in ascending order of timestamps. Usually, a Timeseries represents a collection point that can periodically collect physical quantities of the environment it is in. |
32-
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33-
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
32+
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33+
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
3434

3535
## Distributed Related Concepts
3636

‎src/UserGuide/dev-1.3/Background-knowledge/Cluster-Concept_apache.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@
2323

2424
## Sql_dialect Related Concepts
2525

26-
| Concept | Meaning |
27-
| ----------------------- | ------------------------------------------------------------ |
28-
| sql_dialect | IoTDB supports two time-series data models (SQL dialects), both managing devices and measurement points. Tree: Manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. Table: Manages data in a relational table manner, where one table corresponds to a category of devices. |
29-
| Schema | Schema is the data model information of the database, i.e., tree structure or table structure. It includes definitions such as the names and data types of measurement points. |
30-
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
26+
| Concept | Meaning |
27+
| ----------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
28+
| sql_dialect | Tree model: manages devices and measurement points, manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. |
29+
| Schema | Schema is the data model information of the database, i.e., tree structure. It includes definitions such as the names and data types of measurement points. |
30+
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
3131
| Timeseries | Also known as: physical quantity, time series, timeline, point location, semaphore, indicator, measurement value, etc. It is a time series formed by arranging multiple data points in ascending order of timestamps. Usually, a Timeseries represents a collection point that can periodically collect physical quantities of the environment it is in. |
32-
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33-
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
32+
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33+
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
3434

3535
## Distributed Related Concepts
3636

‎src/UserGuide/dev-1.3/Background-knowledge/Cluster-Concept_timecho.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -23,14 +23,14 @@
2323

2424
## Sql_dialect Related Concepts
2525

26-
| Concept | Meaning |
27-
| ----------------------- | ------------------------------------------------------------ |
28-
| sql_dialect | IoTDB supports two time-series data models (SQL dialects), both managing devices and measurement points. Tree: Manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. Table: Manages data in a relational table manner, where one table corresponds to a category of devices. |
29-
| Schema | Schema is the data model information of the database, i.e., tree structure or table structure. It includes definitions such as the names and data types of measurement points. |
30-
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
26+
| Concept | Meaning |
27+
| ----------------------- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
28+
| sql_dialect | Tree model: manages devices and measurement points, manages data in a hierarchical path manner, where one path corresponds to one measurement point of a device. |
29+
| Schema | Schema is the data model information of the database, i.e., tree structure. It includes definitions such as the names and data types of measurement points. |
30+
| Device | Corresponds to a physical device in an actual scenario, usually containing multiple measurement points. |
3131
| Timeseries | Also known as: physical quantity, time series, timeline, point location, semaphore, indicator, measurement value, etc. It is a time series formed by arranging multiple data points in ascending order of timestamps. Usually, a Timeseries represents a collection point that can periodically collect physical quantities of the environment it is in. |
32-
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33-
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
32+
| Encoding | Encoding is a compression technique that represents data in binary form to improve storage efficiency. IoTDB supports various encoding methods for different types of data. For more detailed information, please refer to:[Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
33+
| Compression | After data encoding, IoTDB uses compression technology to further compress binary data to enhance storage efficiency. IoTDB supports multiple compression methods. For more detailed information, please refer to: [Encoding-and-Compression](../Technical-Insider/Encoding-and-Compression.md) |
3434

3535
## Distributed Related Concepts
3636

0 commit comments

Comments
 (0)