TDengine 3.3.3.0 Release Notes
New Features/Optimizations
- Added function support: pi, truncate/tunc, exp, ln, mod, rand, sign, degrees, radians, char, ascii, position, trim, replace, repeat, substring, substr, substring_index, week, weekday, weekofyear, dayofweek, stddev_pop, var_pop
- Multi-level storage supports Microsoft Object Storage Azure Blob [Enterprise Edition]
- Support for MongoDB data source [Enterprise Edition]
- TDengine supports macOS Enterprise Edition client [Enterprise Edition]
taosX
logs do not write to syslog by default [Enterprise Edition]- Server records all slow query information to the log database
- Added server version number to the query result of
SHOW CLUSTER MACHINES
[Enterprise Edition] - Removed reserved keywords LEVEL/ENCODE/COMPRESS, can be used as column names/table names/database names, etc.
- Dynamic modification of temporary directory is prohibited
- Round function: supports rounding precision
- Timediff function: returns the result of timestamp expr1 - expr2, supports negative results, and approximates to the precision specified by time_unit
- Max/min functions: support strings as input parameters; when input parameters are string types, return the maximum string value
- Improved the performance of
taosX
data synchronization [Enterprise Edition] - Unified storage strategy for slow queries and ordinary logs
- Optimized the issue of large offset files and slow loading in the subscription function
- Upgraded JDBC driver to 3.2.5
- Kafka connector commits changed to synchronous mode
- New parameter: whether to report an exception when the table query does not exist
- Expanded the maximum window of
tsma
interval to 1 year - Supports bulk table creation from CSV files
Issues Fixed
- MQTT write tasks do not automatically restart after server restart [Enterprise Edition]
- Fixed the issue where agent and PI connector connection errors on Windows caused task termination [Enterprise Edition]
- After restarting
taosadapter
, MQTT tasks fail to sync data [Enterprise Edition] - MQTT write task status is incorrect on Explorer [Enterprise Edition]
- Tasks running after restarting
taosX
are not rescheduled [Enterprise Edition] - Optimized log output information for
taosX
MongoDB DataIn tasks [Enterprise Edition] - Fixed the backup failure issue when the
local.toml
file is empty [Enterprise Edition] taosX
replica task data synchronization issue after network disconnection recovery [Enterprise Edition]- Fixed the metadata synchronization issue when upgrading from version 3.1 to 3.3 [Enterprise Edition]
- MQTT tasks cannot automatically recover after
taosadapter
restarts abnormally [Enterprise Edition] - Kafka DataIn task status is normal, but the task stops consuming data [Enterprise Edition]
- Fixed the issue of crash caused by querying
LAST + INTERVAL
- Hot updating
stt_trigger
during data writing causestaosd
to crash taoskeeper
repeatedly restarts after changing the root password- Stream computing cannot continue after service restart in cloud services
tsdb
loading cache causestaosd
deadlock- Error when specifying fill value as 0 during query
LAST_ROW
query results do not match expectations- User specifying
information_schema
database causestaosd
to crash GROUP BY
statements support positional parameters and alias syntax- Metadata cloning function object error causes crash
- Cursor error during data filling when updating cache causes
taosd
to exit abnormally - STDDEV function calculation result is randomly incorrect
- Unable to add offline nodes in multi-level storage and encryption scenarios
taos CLI
cannot input passwords longer than 20 bytes- Error when concatenating SQL for writing: int data overflow
- Consistency of metadata under high concurrent query scenarios
- Attempted to solve the issue where tasks cannot stop when manually clicking the stop button
- Resolved the issue of CSV file export error when columns or tags contain commas or quotes
- Crash caused by concurrent describing of the same subtable in multi-threading
- Query results from the data browser are not displayed according to the configured timezone
- Memory leak issue in
taosadapter
when creating WebSocket connections - Community edition cannot start normally on RedHat operating system
- Invalid assertion causing crash in scenarios where two
stt
are located in data block timeline distribution holes - Issue where S3 fails to pull data after a long time
- Using result set function to determine the orderliness of the timeline
- Solved the issue of slow supertable projection queries
- Fixed: In a multi-node environment, transaction return code inconsistent with transaction status causes transaction backlog
- Fixed: Error of reappearing data after deletion in
stt_trigger = 1
- Excessive memory usage of
taosd
during node recovery leads to OOM - Error in judgment when limit is too small
- Connectivity and obtaining sample data functionality for AVEVA historian data source
- Issue where
taosd
service cannot be stopped normally - Crash caused by querying
LAST
function on fully empty columns - Triggering assert causes core dump when querying
cid
not in the current version of schema - OOM issue when writing message body is too large; increased
syncLogBufferMemoryAllowed
parameter to control - Query error when timezone is set to UTC and data contains "1970"
- Cancel waiting timeout for message synchronization on
mnode
nodes - Authorization status of the cluster becomes invalid after abnormal recovery of cluster nodes
- Query null pointer issue
- When restoring
vnode
, temporarily setvgroup
to single replica - SQL reserved words can be used as column names to create supertables, and can also be used as tag names
- Continuous growth of memory during high-concurrency queries
- Crash caused by assertion failure during checkpoint processing in stream computing
- Fixed the issue in version 3.3.2.8.0820 where tables not found in
information_schema
could be queried - Excessive memory usage of
taosd
during node recovery leads to OOM - Fixed the issue of
taosd
crashing when importing data throughtaosX
under schema change - Possible memory leak
- Client memory leak
- Open source users cannot modify other database options after upgrading
stt_trigger
value - Query results for
NOT IN (NULL)
are incorrect taos shell
andtaosBenchmark
cannot successfully connect to cloud service instances