TDengine is a time-series database<\/a> purpose-built for Industry 4.0 and Industrial IoT. It enables real-time ingestion, storage, analysis, and distribution of petabytes of data per day, generated by billions of sensors and data collectors. With TDengine making big data accessible, valuable, and affordable, digital transformation has never been easier.<\/p>\n\n\n\n You can also run TDengine in Kubernetes or in Docker containers. See Supported Platforms<\/a> for details about the compatibility of TDengine 3.1.1.0 with various architectures and operating systems.<\/p>\n\n\n\n Note:<\/strong> You must upgrade existing clients to TDengine 3.1.1.0 before connecting to a TDengine 3.1.1.0 server.<\/p>\n\n\n\n TDengine Cloud instances will be upgraded automatically, and an account representative will notify you of the next scheduled maintenance window during which your instances will be upgraded. Note that if you manually shut down your instances prior to the maintenance window, those instances will be automatically upgraded to the latest version.<\/p>\n\n\n\n Any TDengine Cloud instances on the legacy Free Plan are automatically upgraded the next time they are shut down. You can manually shut down an instance by opening the Instances<\/strong> tab and clicking the Active<\/strong> slider.<\/p>\n\n\n\n You can check your current version of TDengine at any time by running the You can upgrade TDengine OSS and TDengine Enterprise to version 3.1.1.0 from version 3.0.1.5 or later.<\/p>\n\n\n\n IMPORTANT: If you upgrade to TDengine 3.1.1.0 from any version prior to TDengine 3.1.0.0, you cannot roll back to the previous version. Upgrading to 3.1.1.0 will alter your data such that it cannot be read by versions prior to 3.1.0.0.<\/strong><\/p>\n\n\n\n To upgrade TDengine OSS or TDengine Enterprise, first back up your deployment by making a copy of the TDengine directory. Next, remove all streams from your deployment. You can re-create your streams after the upgrade process is complete.<\/p>\n\n\n\n IMPORTANT: You must remove all streams before upgrading to TDengine 3.1.1.0. If you upgrade a deployment that contains streams, the upgrade will fail and your deployment will become nonoperational.<\/strong><\/p>\n\n\n\n After verifying that your deployment has been backed up and that streams have been removed, install TDengine 3.1.1.0 as described in the official documentation<\/a>. It is not necessary to uninstall TDengine before upgrading.<\/p>\n\n\n\n Note:<\/strong> If you have deployed TDengine as a cluster, you must shut down and upgrade all nodes in the cluster to TDengine 3.1.1.0. Rolling upgrades are not supported in TDengine 3.1.1.0.<\/p>\n\n\n\n If you are running TDengine 2.6 or earlier, contact the TDengine Team for assistance in migrating your deployment to TDengine 3.1.1.0. TDengine Enterprise customers can contact their account representative for support, and all users can join the TDengine Discord<\/a> server and request help from the team.<\/p>\n\n\n\nWhat’s New<\/h2>\n\n\n\n
\n
VARBINARY<\/code> data type:<\/strong> You can now store variable-length binary data with the VARBINARY<\/code> data type.
Note: For historical reasons, the BINARY<\/code> type can also contain variable-length data. Starting with version 3.1.1.0, using BINARY<\/code> to store variable-length data is deprecated. However, existing BINARY<\/code> columns that contain variable-length data will continue to function as in previous versions.<\/li>\n\n\n\nPARTITION BY<\/code> clause with an SLIMIT<\/code> clause has been significantly improved. In addition, performance is improved for JOIN<\/code> operations on supertables.<\/li>\n\n\n\nCompatibility<\/h2>\n\n\n\n
\n
Upgrading to TDengine 3.1.1.0<\/h2>\n\n\n\n
Upgrading TDengine Cloud<\/h3>\n\n\n\n
SELECT SERVER_VERSION();<\/code> command.<\/p>\n\n\n\nUpgrading TDengine OSS and TDengine Enterprise<\/h3>\n\n\n\n
Resolved Issues<\/h2>\n\n\n\n