Apache IoTDB 2.0.1-beta

Features & Improvements

• 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.
• 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.
• 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.
• Data Query: Users can control the loading of UDF, PipePlugin, Trigger, and AINode via URI with configuration items to load JAR packages.
• Storage Engine: The table model supports data ingestion through the Session interface, and the Session interface supports automatic metadata creation.
• Storage Engine: The Python client now supports four new data types: String, Blob, Date, and Timestamp.
• Storage Engine: The comparison rules for the priority of same-type merge tasks have been optimized.
• Data Synchronization: Support for specifying authentication information of the receiving end at the sending end.
• Stream Processing Module: TsFile Load now supports the table model.
• Stream Processing Module: Pipe now supports the table model.
• System Management: The Benchmark tool has been adapted to support the table model.
• System Management: The Benchmark tool now supports four new data types: String, Blob, Date, and Timestamp.
• System Management: The stability of DataNode scaling down has been enhanced.
• System Management: Users are now allowed to perform drop database operations in readonly mode.
• Scripts and Tools: The import-data/export-data scripts have been extended to support new data types (string, binary large objects, date, timestamp).
• 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.
• Ecosystem Integration: Support for Kubernetes Operator.
  ...

Bugs

• Fixed the issue where the query result set contained duplicate timestamps.
• Fixed the issue where deleted data could be queried again when triggered to merge after deletion.
• Fixed the issue where the target sequence in SELECT INTO containing backticks would result in writing the wrong sequence.
• 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.
• Fixed the issue where MergeReader needed to consider memory allocation to avoid negative available memory during out-of-order and reverse queries.
• Fixed the issue where the CN in the cluster could not register large pipe plugins (greater than 100MB) and the parameters were not configurable.
• Fixed the issue of controlling the memory size of TimeIndex referenced by Pipe for TsFileResource.
• Fixed the issue where the Storage Engine - File Count - mods displayed negative values on the monitoring dashboard.
• Fixed the issue where the query result order was incorrect in the C# client.

...