Release Announcement: InfluxDB OSS 2.0.2

Navigate to:

A new maintenance release for InfluxDB OSS is available now.  Thank you to all the community members who have downloaded and used this latest release.  We’ve gotten a couple of important defects addressed here and made some other improvements based on early feedback.

This maintenance release of InfluxDB OSS includes the following fixes and improvements:

  • Upgrading from 1.x to 2.x
    • The upgrade command now checks to see if you have continuous queries running and automatically exports them to a local file.
    • If you've been running with auth-enabled = false in your 1.x setup, a warning now appears as this is not an option in 2.x. If you see this warning, it is recommended to reconfigure your 1.x instance with auth-enabled = true and ensure all of the username/password combinations are working as expected before retrying the upgrade process.
  • CLI Improvements
    • The 1.x database and retention policy mappings (DBRP) required to allow InfluxQL queries against the underlying 2.0 buckets can now be managed through the CLI. Documentation has been updated to describe how to leverage the CLI and administer these mappings.
  • Flux and Developer Tools
    • Flux has advanced to the latest version, and we've also made improvements to the underlying LSP.
    • We've added documentation for the Flux Visual Studio Code plugin and for leveraging the LSP natively through tools like Vim.
  • UX improvements
    • Task runs can be filtered by time.
    • Chronograf and Grafana users were reporting multiple entries for 1.x database and retention policies after migration. This has been addressed.
  • Security
    • Backup/Restore now uses the --skip-verify flag for backup/restore CLI command.
    • Scrapers can also be configured to use self-signed certificates.

The binaries for the latest open source release can be found on our downloads page.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our InfluxDB GitHub Repo or our Community Site and we will take a look.