|
19 | 19 |
|
20 | 20 | --> |
21 | 21 |
|
| 22 | +# Apache IoTDB 2.0.1-beta |
| 23 | + |
| 24 | +## Features & Improvements |
| 25 | + |
| 26 | +- Table Model: IoTDB has introduced a new model named table model, and supports standard SQL query syntax, including SELECT, WHERE, JOIN, GROUP BY, ORDER BY, LIMIT clause and subQuery. |
| 27 | +- Data Query: The table model supports a variety of functions and operators, including logical operators, mathematical functions, and the time-series specific function DIFF, etc. |
| 28 | +- Data Query: The databases of the table model and tree model are invisible to each other, and users can choose the appropriate model based on their needs. |
| 29 | +- Data Query: Users can control the loading of UDF, PipePlugin, Trigger, and AINode via URI with configuration items to load JAR packages. |
| 30 | +- Storage Engine: The table model supports data ingestion through the Session interface, and the Session interface supports automatic metadata creation. |
| 31 | +- Storage Engine: The Python client now supports four new data types: String, Blob, Date, and Timestamp. |
| 32 | +- Storage Engine: The comparison rules for the priority of same-type merge tasks have been optimized. |
| 33 | +- Data Synchronization: Support for specifying authentication information of the receiving end at the sending end. |
| 34 | +- Stream Processing Module: TsFile Load now supports the table model. |
| 35 | +- Stream Processing Module: Pipe now supports the table model. |
| 36 | +- System Management: The Benchmark tool has been adapted to support the table model. |
| 37 | +- System Management: The Benchmark tool now supports four new data types: String, Blob, Date, and Timestamp. |
| 38 | +- System Management: The stability of DataNode scaling down has been enhanced. |
| 39 | +- System Management: Users are now allowed to perform drop database operations in readonly mode. |
| 40 | +- Scripts and Tools: The import-data/export-data scripts have been extended to support new data types (string, binary large objects, date, timestamp). |
| 41 | +- Scripts and Tools: The import-data/export-data scripts have been iterated to support the import and export of three types of data: TsFile, CSV, and SQL. |
| 42 | +- Ecosystem Integration: Support for Kubernetes Operator. |
| 43 | + ... |
| 44 | + |
| 45 | +## Bugs |
| 46 | + |
| 47 | +- Fixed the issue where the query result set contained duplicate timestamps. |
| 48 | +- Fixed the issue where deleted data could be queried again when triggered to merge after deletion. |
| 49 | +- Fixed the issue where the target sequence in SELECT INTO containing backticks would result in writing the wrong sequence. |
| 50 | +- Fixed the issue where an array out-of-bounds exception was thrown in the HAVING clause of the tree model due to a non-existent column name. |
| 51 | +- Fixed the issue where MergeReader needed to consider memory allocation to avoid negative available memory during out-of-order and reverse queries. |
| 52 | +- Fixed the issue where the CN in the cluster could not register large pipe plugins (greater than 100MB) and the parameters were not configurable. |
| 53 | +- Fixed the issue of controlling the memory size of TimeIndex referenced by Pipe for TsFileResource. |
| 54 | +- Fixed the issue where the Storage Engine - File Count - mods displayed negative values on the monitoring dashboard. |
| 55 | +- Fixed the issue where the query result order was incorrect in the C# client. |
| 56 | + |
| 57 | +... |
| 58 | + |
22 | 59 | # Apache IoTDB 1.3.3 |
23 | 60 |
|
24 | 61 | ## Features & Improvements |
|
0 commit comments