This topic describes the release notes for the engine versions of Lindorm Time Series Database (TSDB). For more information about the version description and the download of TSDB SDK, see Version description.
V2.6.13 released on April 30, 2021
The following issue is fixed: Behavior inconsistency occurs due to uncaught exceptions when you use the IgnoreError mode.
The following issue is fixed: No data is returned for a query when the startTime parameter is set to an excessively early point in time.
V2.6.12 released on April 9, 2021
Audit logs that record data writes are added. This feature negatively affects the write performance. Therefore, if you want to enable this feature, you must submit a ticket. When you perform O&M, you can query audit logs only in the background.
V2.6.11 released on April 2, 2021
roffset and rlimit are added to
api/query/mlast. The syntax of roffset is compatible with that of tupleOffset. The syntax of rlimit is compatible with that of tupleLimit.
The issue related to the valid range of timestamps is fixed.
The following issue is fixed: An error is reported when the metric that you want to query does not exist.
V2.6.10 released on February 25, 2021
The metrics storage usage and timeline usage for TSDB instances are added. This way, you can create alert rules for these metrics in the CloudMonitor console.
The following issue is fixed: Internal errors occur when global limits are used.
The following issue is fixed: The IgnoreError mode does not take effect.
V2.6.9 released on January 27, 2021
The performance of the latest value queries is optimized.
The following issue is fixed: The number of timelines cannot be reset immediately after a TRUNCATE operation is performed.
The following issue is fixed: The node status is not reset after an unplanned restart when an asynchronous task is performed.
V2.6.7 released on January 14, 2021
The prefix of a field value can be used as a match condition in multi-value data queries.
The number of nodes can be increased for an instance scale-up in Standard Edition II, Ultimate Edition I, and Ultimate Edition II.
The blank screen time of slow query logs can be reduced. For more information about slow query logs, see Slow query logs.
The memory leak issue is fixed for TSQL.
The following issue is fixed: An error occurs if a field that you want to query does not exist when a multi-value query runs.
V2.6.6 released on January 7, 2021
The formatted content in slow query logs can be downloaded.
V2.6.5 released on December 30, 2020
The global limit feature can be applied to the total number of data points that are returned for your query.
Hints can be pushed down to make queries efficient.
The following issue is fixed: The query result is empty due to a null pointer exception in your query.
V2.6.4 released on December 3, 2020
Spatial data can be written and queried. This feature is in public preview. To apply for a free trial, submit a ticket.
The following issue is fixed: An error occurs during user authentication due to the created
The following issue is fixed: Nodes may fail to start when multiple nodes are started in parallel.
V2.6.3 released on October 14, 2020
Query hints can be specified in query criteria. For more information about this feature, see query hint description.
The following two features are supported: time series forecasting and time series forecasting for anomaly detection. For more information, see Time series forecasting and Time series forecasting for anomaly detection (abnormaldetect).
Some errors can be ignored when data is written in batches.
The following issue is fixed: No data is returned when the query conditions contain the specified tag keys and tag values.
V2.6.2 released on August 13, 2020
Byte-array data can be written and queried.
V2.6.1 released on July 30, 2020
Tuples can be used to filter data when a multi-value query runs. You can specify filter conditions in WHERE clauses.
Reverse queries are supported.
The following issue is fixed: An error occurs when the specified tag values do not exist in multi-value data queries.
The following issue is fixed: When data written to existing timelines is out of order due to cache replacement, the written data cannot be queried.
The following issue is fixed: A memory issue occurs on the engine when the heap memory is inappropriately used.
V2.6.0 released on June 29, 2020
INSERT statements are supported for TSQL.
The following issue is fixed: A memory issue occurs if an excessively large number of connections exist in a connection pool.
The following issue is fixed: The millisecond-level data in downsampling expressions cannot be parsed.
The following issue is fixed: An error can occur if you run queries to query the latest multi-value data.
V2.5.14 released on May 19, 2020
The aggregate functions
rlastthat return the actual timestamp versions can be added to downsampling expressions.
The following issue is fixed: A memory leak can occur in internal caches.
The following issue is fixed: Unplanned large queries are run because downsampling expressions are incorrectly parsed.
V2.5.13 released on March 19, 2020
The account management feature is supported. You can manage accounts based on basic access authentication. For more information, see Manage accounts.
The following issue is fixed: An error occurs when you use wildcards to match tags.
V2.5.12 released on January 16, 2020
Prefix matching and suffix matching can be added as query filters.
The following issue is fixed: JSON fields are incorrectly used because the
api/query/lastoperation does not perform strict authentication on JSON fields.
V2.5.11 released on November 21, 2019
The following issue is fixed: The time window in a query result is invalid when the specified time granularity for downsampling is weeks in the calendar form.
The following issue is fixed: The result returned by the COUNT function is invalid when
preDpValueis used to filter values in a query.
The following issue is fixed: The
rateoperators are mixed in the multi-value data model.
V2.5.10 released on October 16, 2019
The following issue is fixed: Data of monitoring metrics in TSDB is invalid.
V2.5.9 released on September 3, 2019
A delta operator is supported for queries.
The following issue is fixed: A tag filter in the
tagsfield fails to be parsed, but the same tag filter in the
filtersfield is correctly parsed.
V2.5.8 released on August 6, 2019
A median operator is supported for downsampling.
The following issue is fixed: The number of data points returned by
/api/suggestcannot reach the specified maximum number.
V2.5.7 released on July 19, 2019
The multi-value data model is supported for TSQL.
Instance specifications are added.
V2.5.6 released on June 27, 2019
The preprocessing feature for time series data is added.
api/mqueryoperations, data can be queried based on filter conditions.
V2.5.4 released on June 13, 2019
The following issue is fixed: A backward compatibility issue exists in the response header
V2.5.3 released on June 10, 2019
API operation changes
tag key, or
tag valuespecified in your query condition does not exist, no error is reported and an empty result set is returned.
The following issue is fixed: Query failures occur when
Prometheuspushes down aggregation operators that TSDB does not support.
V2.5.2 released on May 18, 2019
The aggregation algorithm stddev is supported.
If the result set returned by
api/query/mlastis in the format specified by
tupleFormat, the result set can be displayed by page.
V2.5.1 released on April 26, 2019
The following issue is fixed: When the details parameter or the summary parameter is added to your /api/put or /api/mput request, the data point statistics are invalid.
The following issue is fixed: When a single data point is written, data in the JSON format fails to be parsed because the data point contains a space.
The following issue is fixed: A null pointer exception exists in the multi-value data model.
The following issue is fixed: The number of timelines in TSDB keeps increasing and cannot be limited.
The following issue is fixed: If a timeline fails to be deleted, some schema information of your multi-value data is retained.
V2.5.0 released on April 13, 2019
TSQL is released. TSQL is a structured query language that is used in TSDB. TSQL makes development easy. TSQL can be used to perform a wide range of computing operations on time series data. For example, TSQL can be used to join multiple metrics. TSQL also provides powerful capabilities for analyzing business metrics. For more information, see Quick start for TSQL.
TSDB for Prometheus is released. The remote storage adapter for Prometheus is added to the TSDB engine so that the engine can seamlessly connect to the open source self-managed Prometheus service. This way, you can efficiently monitor Kubernetes clusters. TSDB for Promethues
V2.4.2 released on March 20, 2019
The api/truncate operation is used to clean dirty data. For more information, see Clean data.
Some stability issues are fixed.
V2.4.1 released on February 28, 2019
The following issue is fixed: The integrity of retrieved data is negatively affected due to index updates.
V2.4.0 released on February 14, 2019
The multi-value data model for time series data is released. Downsampling and aggregation for multiple metrics is supported. For more information, see Developer guide.
V2.3.8 released on January 24, 2019
The tag parameter is used as an optional parameter when data is written. Data queries and writes without specified tags are supported.
Queries without specified tags are optimized.
Timeline queries are optimized to make queries stable.
The following issue is fixed: The max field in your /api/dump_meta request does not take effect.
V2.3.3 released on November 27, 2018
The instances whose specifications range from mlarge to 24xlarge can be scaled up or scaled down. These instances can also be scaled out or scaled in.
Auto-renewal is supported for TSDB instances. You can enable auto-renewal for TSDB instances that use the subscription billing method.
V2.3.1 released on October 20, 2018
The time parameter can be configured for the query/last operation. This way, the latest business data generated before the specified point in time can be queried. Data timestamps are used to specify points in time.
Millisecond granularity of data reads and writes is supported. The msResolution parameter specifies the time granularity of data reads. By default, the value of the msResolution parameter is false. The value false specifies that the time granularity for data writes is the same as the time granularity for data reads. If the msResolution parameter is set to true, the time granularity for all returned data is milliseconds.
TSDB SDK supports filtering of multi-value data points. If multi-value data points are written by using TSDB SDK, the values of multiple metrics can be combined to filter the data and all of the values for these metrics are returned. For more information, see the topics related to TSDB SDK.
The spatio-temporal feature is released. GPS data can be written, filtered, and analyzed. You can submit a ticket to use the feature for testing.
V2.3.0 released on October 9, 2018
The TSDB engine is updated. For 48xlarge and 96xlarge instances, the number of timelines that can be written is unlimited. For instances of other specifications, the maximum number of timelines that can be written is increased to 10 times the original maximum number of timelines.
V2.2.8 released on August 10, 2018
Data generated at a single point in time can be queried.
Data that uses the millisecond granularity can be read, written, or downsampled.
The following time units of downsampling are added: month and year.
The following two operators are added for data filling policies: near and after.
The following issue is fixed: The monitoring data of time series and disks is invalid.
The following issue is fixed: The metadata of time series can still be retrieved after the time series are cleared.
The following issue is fixed: The type of read data is inconsistent with the type of written data.
The following issue is fixed: The monitoring data about write rates and disks is invalid.
V2.2.7 released on July 6, 2018
TSDB SDK is updated. The updated version of TSDB SDK can be used to write, query, and analyze multi-value data points.
V2.2.4 released on May 24, 2018
Data of the STRING and BOOLEAN data types can be written.
The last operation is provided to query the latest data point in a time series.
The following issue is fixed: The result of deleting timelines is invalid in specific conditions.
V2.2.3 released on April 10, 2018
The O&M monitoring and alerting are added.
TSDB instances can be connected to Realtime Compute for Apache Flink. Realtime Compute for Apache Flink provides a stream computing engine.
TSDB instances can be connected to Grafana. Grafana is a tool that is used to visualize data.
The billing method of a TSDB instance can be changed from pay-as-you-go to subscription in the TSDB console.
The query results can be returned by page.
The following three data filling policies are added: linear, previous, and fixed. linear represents linear interpolation. previous means that a value is interpolated based on the preceding value. fixed means that a fixed value is interpolated.
Data points are filtered by metric value.
Inverted indexes are supported.
Abnormal query requests can be processed. This includes the requests that timed out and requests in which the specified parameters are invalid.
Access to the pipeline aggregation engine is optimized.
The limits on special characters in tag names and metric names are removed.
The following issue is fixed: The operations for deleting data or metrics do not take effect.
The following issue is fixed: The Instances page in the TSDB console does not appear as expected.
The following issue is fixed: An error is returned when you run concurrent queries.
V1.2.0 released on February 7, 2018
The stability of TSDB instances is optimized. The following issue is fixed: Services provided by TSDB instances are unstable when large queries are run.
By default, the downsampled data for an instance is calculated based on the local time zone of the region where the instance is deployed.
The following issue is fixed: When you query tag values in the TSDB console, the returned tag values are incomplete.
V1.1.2 released on November 30, 2017
The getlastdp operation is provided to query the latest data values of time series.
TSDB is available in the China (Shenzhen) region. The China (Shenzhen) region has three zones Zone A, Zone B, and Zone C.
The API operation that is used to delete timelines is optimized.
V1.1.1 released on November 16, 2017
A TSDB instance can be accessed over the Internet or a virtual private cloud (VPC).
V1.1.0 released on November 3, 2017
TSDB Client for Java 1.0.0 is released. It provides a wide range of features, such as standard API operations, non-blocking I/O operations, instance protection, automated delivery of data in batches, and automated connection management.
Timelines can be deleted by calling an API operation or by performing operations in the TSDB console. Millions of timelines can be deleted within a few seconds.
Instances are protected. The number of data points can be specified in a single request to ensure instance availability.
TSDB is available in the China (Qingdao) and China (Beijing) regions.
Automated O&M is supported. Alerts can be automatically sent if instances become unavailable.
The following issue is fixed: An instance becomes unavailable due to a long query time range.
The following issue is fixed: An instance becomes unavailable because the underlying API operations for asynchronous requests are incompatible.
V1.0.2 released on September 15, 2017
TSDB can connect to Resource Access Management (RAM) so that Alibaba Cloud accounts, RAM users, and the permissions on instance resources can be managed.
V1.0.1 released on August 28, 2017
TSDB can be connected to CloudMonitor. Alert notifications can be sent based on the instance metrics that are monitored.
The process for creating an instance is optimized. The Instances page shows the progress for creating an instance in real time.
The instance configuration is optimized. The maximum number of tags for a single timeline is increased to 16.
The following issue is fixed: The name of an instance is not specified. However, after the instance is created, the instance name appears.
The following issue is fixed: A curve for instance monitoring does not appear as expected.
The following issue is fixed: An instance can be created if no VPCs are available, but the instance cannot be used.
V1.0.0 released on July 31, 2017
TSDB V1.0.0 is officially released in public preview. TSDB V1.0.0 provides the following features:
Time series data that complies with the OpenTSDB protocol can be read and written.
Data can be highly compressed before the data is stored. The storage that is required for a single data point is less than 2 bytes.
Data Management (DMS)
Data validity: Data validity periods can be customized. Data automatically becomes invalid after the customized data validity period ends. The expired data is automatically deleted.
Data deletion: Useless data or dirty data can be automatically deleted to release the storage space.
Data query: Data can be randomly queried on the web UI.
Instance monitoring alert
The following three core metrics can be monitored in the TSDB console in real time: the number of write operations per second, the total number of stored timelines, and the used storage.
By default, TSDB instances can be connected only over VPCs. This secures instance connections.
The whitelist of an instance can be configured to protect your instance and ensure data security.