This is an automated email from the ASF dual-hosted git repository.
haonan pushed a commit to branch rc/2.0.2
in repository https://gitbox.apache.org/repos/asf/iotdb.git
The following commit(s) were added to refs/heads/rc/2.0.2 by this push:
new 05bfec6a69e Update info before release
05bfec6a69e is described below
commit 05bfec6a69e373442761fc99ef8e7cea45377ef1
Author: HTHou <[email protected]>
AuthorDate: Mon Apr 14 10:34:04 2025 +0800
Update info before release
---
RELEASE_NOTES.md | 66 +++++++++++++++++++++++++
iotdb-client/client-py/resources/pyproject.toml | 2 +-
iotdb-client/jdbc/src/main/feature/feature.xml | 2 +-
iotdb-core/ainode/pyproject.toml | 2 +-
4 files changed, 69 insertions(+), 3 deletions(-)
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 359af0cba5c..e7ffb48d94d 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -18,6 +18,72 @@
under the License.
-->
+# Apache IoTDB 2.0.2
+
+## Features & Improvements
+
+- Data Query: Added management of table model UDFs, including user-defined
scalar functions (UDSF) and user-defined aggregate functions (UDAF).
+- Data Query: Table model now supports permission management, user management,
and authorization for related operations.
+- Data Query: Introduced new system tables and various O&M statements to
optimize system management.
+- System Management: The tree model and table model are now fully isolated at
the database level.
+- System Management: The built-in MQTT Service is now compatible with the
table model.
+- System Management: The CSharp client now supports the table model.
+- System Management: The Go client now supports the table model.
+- System Management: Added a C++ Session write interface for the table model.
+- Data Synchronization: The table model now supports metadata synchronization
and synchronization delete operations.
+- Scripts and Tools: The import-data/export-data scripts now support the table
model and local TsFile Load.
+- ...
+
+## Bugs
+
+- Fixed the memory leak issue when writing data using SQL.
+- Fixed the issue of duplicate timestamps appearing in table model queries.
+- Fixed the issue of duplicate removal anomaly in table model aggregate
queries with GROUP BY.
+- Fixed the handling of Long.MIN_VALUE or Long.MAX_VALUE during write and
merge processes.
+- Fixed the issue of Long.MIN_VALUE timestamp causing time partition overflow
and subsequent load failure.
+- Fixed the issue of out-of-order data within a single TSFile on the
destination data node during region migration in load operations.
+- Fixed the issue where Explain Analyze caused the execution plan to fail to
properly perform column pruning.
+- Fixed the issue where the C# Session could not correctly fetch result sets
when querying large amounts of data (exceeding fetch_size) on a cluster with
more than one node.
+- Fixed the inconsistency in reading JDK environment variables by ConfigNode
and DataNode on Windows.
+- Fixed the issue where the query distribution time statistics in Explain
Analyze were larger than actual values, and changed the query distribution time
monitoring from FI level to Query level.
+ ...
+
+# 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.
+
+...
# Apache IoTDB 1.3.3
diff --git a/iotdb-client/client-py/resources/pyproject.toml
b/iotdb-client/client-py/resources/pyproject.toml
index 09a94636e64..bd8ea77a3e2 100644
--- a/iotdb-client/client-py/resources/pyproject.toml
+++ b/iotdb-client/client-py/resources/pyproject.toml
@@ -42,7 +42,7 @@ dependencies = [
"thrift>=0.14.1",
"pandas>=1.0.0",
"numpy>=1.0.0",
- "sqlalchemy<1.5,>=1.4",
+ "sqlalchemy>=1.4",
"sqlalchemy-utils>=0.37.8"
]
diff --git a/iotdb-client/jdbc/src/main/feature/feature.xml
b/iotdb-client/jdbc/src/main/feature/feature.xml
index 033fe46d47c..bbb8f475b9d 100644
--- a/iotdb-client/jdbc/src/main/feature/feature.xml
+++ b/iotdb-client/jdbc/src/main/feature/feature.xml
@@ -18,7 +18,7 @@
-->
<features xmlns="http://karaf.apache.org/xmlns/features/v1.5.0";
name="driver-s7-feature">
- <feature name="iotdb-feature" description="iotdb-feature" version="1.3.3">
+ <feature name="iotdb-feature" description="iotdb-feature" version="2.0.2">
<details>Feature to install required Bundle to use IoTDB inside Karaf
container</details>
<feature prerequisite="true">wrap</feature>
<feature>scr</feature>
diff --git a/iotdb-core/ainode/pyproject.toml b/iotdb-core/ainode/pyproject.toml
index efbbdb1edaf..e690a50112d 100644
--- a/iotdb-core/ainode/pyproject.toml
+++ b/iotdb-core/ainode/pyproject.toml
@@ -21,7 +21,7 @@ build-backend = "poetry.core.masonry.api"
[tool.poetry]
name = "apache-iotdb-ainode"
-version = "2.0.0.dev"
+version = "2.0.2"
description = "Apache IoTDB AINode"
readme = "README.md"
authors = ["Apache Software Foundation <[email protected]>"]
