Supplement 2.0.0 version UserGuide and modify Download #365
Conversation
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
docs/src/Download/README-LATEST.md
Outdated
There was a problem hiding this comment.
Only one readme is enough for “download.”
There was a problem hiding this comment.
Separate the zh and en docs into two directories.
| @@ -24,42 +24,45 @@ | |||
|
|
|||
| To manage industrial IoT timing data, the measurement point data model of TsFile includes the following information | |||
There was a problem hiding this comment.
To manage industrial IoT time series data, the data model of TsFile includes the following concepts
| - TAG：Tag Column | ||
| - name（String）：Column Name | ||
| - dataType（TSDataType）：Data Type | ||
| - FIELD：Field Column | ||
| - name（String）：Column Name | ||
| - dataType（TSDataType）：Data Type |
There was a problem hiding this comment.
-
Tag: (注意使用英文冒号) The description of an IoT device of one dimension in the form of a string key-value pair. For example, "category=XT451" describes the category of a wind turbine is "XT451" and "year=2021" says it is built in the year 2021.
-
Field: A variable that is being measured by a device. Like fan speed, voltage, temperature, wind speed, and so on. Unlike a Tagthat is currently fixed to STRING data type, Fields are supported by various data types.
-
Timestamp and Timeseries: Each value of a FIELD measured by a device is associated with a unique timestamp. The sequence of the timestamps and values of a FIELD is a Timeseries.
-
Schema: A set of Tags that can uniquely identify a kind of device, and the set of Fields that are measured by these devices. E.g., a wind turbine can be uniquely located by "Province," "City," "WindField," and "SerialNumber," so the TAG set of SCHEMA "wind_turbine" can be "Province," "City," "WindField," and "SerialNumber." While its the FIELD set contains "FanSpeed," "Voltage," "Temperature," "WindSpeed," and so on.
-
DeviceId: The unique identifier of an IoT device, which consists of the schema name and all tag values. For example, for the Schema "wind_turbine" above, a DeviceId can be ("wind_turbine", "Beijing", "Beijing", "Field_1135", "T1523678").
|
|
||
| ## Example | ||
|
|
||
| A table is a collection of devices with the same pattern. As shown in the figure below, it is a modeling management of factory equipment, and the physical quantity collection of each device has certain commonalities (such as collecting temperature and humidity physical quantities, collecting physical quantities of the same device on the same frequency, etc.), so it can be managed on a device by device basis. |
There was a problem hiding this comment.
A table is -> A schema describes
it is a modeling management -> it models the management
physical quantity -> physical variable
device by device -> device-by-device
| At this point, a physical device can be uniquely identified through [Region] - [Factory] - [Equipment] (orange column in the figure below, also known as device identification information). The final indicators collected by the device are [Temperature], [Humidity], [Status], and [Arrival Time] (blue column in the figure below). | ||
|
|
There was a problem hiding this comment.
identified through -> identified through 3 Tags
The final indicators -> The Fields
|
|
||
| Used to write data to tsfile | ||
|
|
||
| ```shell |
| // Column Name | ||
| public ColumnSchemaBuilder name(String columnName); | ||
|
|
||
| // The data category of the column |
| // Move the cursor to the next line and return whether there is still data | ||
| boolean next(); |
…, and only keep one readme for “download.”
No description provided.