# Release version

Version IoTDB Binaries IoTDB Sources release notes
0.13.0 All-in-one SHA512 ASC Sources SHA512 ASC release notes
Grafana-plugin SHA512 ASC
Grafana-connector SHA512 ASC
0.12.5 All-in-one SHA512 ASC Sources SHA512 ASC release notes
Server SHA512 ASC
Cluster SHA512 ASC
Grafana-connector SHA512 ASC

Legacy version are available here: https://archive.apache.org/dist/iotdb/ (opens new window)

Attention:

  • Recommended OS parameters

    • Set the somaxconn as 65535 to avoid "connection reset" error when the system is under high load.
      # Linux
      > sudo sysctl -w net.core.somaxconn=65535
       
      # FreeBSD or Darwin
      > sudo sysctl -w kern.ipc.somaxconn=65535
      
      1
      2
      3
      4
      5
  • How to upgrade a minor version (e.g., from v0.12.3 to v0.12.5)?

    • versions which have the same major version are compatible.
    • Just download and unzip the new version. Then modify the configuration files to keep consistent with what you set in the old version.
    • stop the old vesion instance, and start the new one.
  • How to upgrade from v.13.x to v0.14.x?

    • Version 0.14 has changed the SQL syntax conventions (please refer to the syntax conventions section of the user manual), the incompatibilities are as follows:
      • Identifiers that are not quoted with backquotes are not allowed to be pure numbers and only allowed to contain letters, Chinese characters, and underscores. If the above occurs in an identifier, use backquotes to enclose the identifier.
      • Identifiers no longer support quoting with single and double quotes, please use backquotes instead.
      • When using the path node name in the Session API, it needs to be consistent with that in the SQL statement. If the path node is a pure number 111, it needs to be enclosed in backquotes in the SQL statement and written as `111`, then when using the Session API, the corresponding parameter also needs to be written as `111`.
    • In order to ensure the stability of UDF-related APIs, in version 0.14, UDF-related APIs are separated into an independent module and no longer depend on the tsfile package. The implemented UDFs need to rewrite the code, replace TsDataType with Type, and replace org .apache.iotdb.tsfile.utils.Binary with org.apache.iotdb.udf.api.type.Binary, then redo the packaging and loading process.
  • How to upgrade from v.12.x to v0.13.x?

    • The data format (i.e., TsFile data) of v0.12.x and v0.13.x are compatible, but the WAL file is incompatible. So, you can follow the steps:
    • Execute SET STSTEM TO READONLY command in CLI.
    • Stop writing new data.
    • Execute flush command to close all TsFiles.
    • We recommend to back up all data files before upgrading for rolling back.
    • Just download, unzip v0.13.x.zip, and modify conf/iotdb-engine.properties, especially the unchangeable configurations like timestamp precision. Let all the directories point to the data folder set in v0.12.x (or the backup folder). You can also modify other settings if you want.
    • Stop IoTDB v0.12.x instance, and then start v0.13.x.
    • After the steps above, please make sure the iotdb_version in data/system/schema/system.properties file is 0.13.x. If not, please change it to 0.13.x manually.
    • NOTICE: V0.13 changes many settings in conf/iotdb-engine.properties, so do not use v0.12's configuration file directly.
    • In 0.13, the SQL syntax has been changed. The identifiers not enclosed in backquotes can only contain the following characters, otherwise they need to be enclosed in backquotes.
      • [0-9 a-z A-Z _ : @ # $ { }] (letters, digits, some special characters)
      • ['\u2E80'..'\u9FFF'] (UNICODE Chinese characters)
    • In 0.13, if the path node name in the SELECT clause consists of pure numbers, it needs to be enclosed in backquotes to distinguish it from the constant in the expression. For example, in the statement "select 123 + `123` from root.sg", the former 123 represents a constant, and the latter `123` will be spliced with root.sg, indicating the path root.sg.`123`.
  • How to upgrade from v.11.x or v0.10.x to v0.12.x?

    • Upgrading from v0.11 or v0.10 to v0.12 is similar as v0.9 to v0.10. The upgrade tool will rewrite the data files automatically.
    • Stop writing new data.
    • Call flush command using sbin/start-cli.sh in original version to close all TsFiles.
    • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
    • Just download, unzip v0.12.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in previous version (or the backup folder). You can also modify other settings if you want. Any other config changes in v0.11 should be moved to v0.12.
    • Stop IoTDB v0.11 or v0.10 instance, and start v0.12.x, then the IoTDB will upgrade data file format automatically. It is ok to read and write data when the upgrading process works.
    • After a log All files upgraded successfully! printed, the upgrading completes.
    • NOTICE 1: V0.12 changes many settings in conf/iotdb-engine.properties, so do not use previous configuration file directly.
    • NOTICE 2: V0.12 doesn't support upgrade from v0.9 or lower version, please upgrade to v0.10 first if needed.
    • NOTICE 3: We don't recommend to delete data before the upgrading finished. The deletion will fail if you try to delete data in the storage group with upgrading files.
  • How to upgrade from v.10.x to v0.11.x?

    • The data format (i.e., TsFile data) of v0.10.x and v0.11 are compatible, but the WAL file is incompatible. So, you can follow the steps:
    • Stop writing new data.
    • Call flush command using sbin/start-cli.sh in v0.10.x to close all TsFiles.
    • We recommend to backup the the wal files and mlog.txt before upgrading for rolling back.
    • Just download, unzip v0.11.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the data folder set in v0.10.x (or the backup folder). You can also modify other settings if you want.
    • Stop IoTDB v0.10.x instance, and start v0.11.x, then the IoTDB will upgrade data file format automatically.
    • NOTICE: V0.11 changes many settings in conf/iotdb-engine.properties, so do not use v0.10's configuration file directly.
  • How to upgrade from v0.9.x to v0.10.x?

    • Upgrading from v0.9 to v0.10 is more complex than v0.8 to v0.9.
    • Stop writing new data.
    • Call flush command using sbin/start-client.sh in v0.9 to close all TsFiles.
    • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
    • Just download, unzip v0.10.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in v0.9.x (or the backup folder). You can also modify other settings if you want.
    • Stop IoTDB v0.9 instance, and start v0.10.x, then the IoTDB will upgrade data file format automatically.
  • How to upgrade from 0.8.x to v0.9.x?

    • We recommend to backup the data file (also the wal files and mlog.txt) before upgrading for rolling back.
    • Just download, unzip v0.9.x.zip, and modify conf/iotdb-engine.proeprties to let all the directories point to the folders set in v0.8.x (or the backup folder). You can also modify other settings if you want.
    • Stop IoTDB v0.8 instance, and start v0.9.x, then the IoTDB will upgrade data file format automatically.

# All releases

Find all releases in the Archive repository (opens new window).

# Verifying Hashes and Signatures

Along with our releases, we also provide sha512 hashes in *.sha512 files and cryptographic signatures in *.asc files. The Apache Software Foundation has an extensive tutorial to verify hashes and signatures (opens new window)which you can follow by using any of these release-signing KEYS (opens new window).

Copyright © 2022 The Apache Software Foundation.
Apache and the Apache feather logo are trademarks of The Apache Software Foundation

Have a question? Connect with us on QQ, WeChat, or Slack. Join the community now.

We use Google Analytics to collect anonymous, aggregated usage information.