« Changelog History


influxdb v2.0.3 Release Notes

Release Date: 2020-12-14 // over 3 years ago

  • 👍 ARM Support

    🚀 This release includes our initial ARM64 preview build.

    💥 Breaking Changes

    ⬆️ influxd upgrade

    ⬆️ Previously, influxd upgrade would attempt to write upgraded config.toml files into the same directory as the source ⚠ influxdb.conf file. If this failed, a warning would be logged and config.toml would be written into the HOME directory.

    🚀 This release breaks this behavior in two ways:

    0️⃣ 1. By default, config.toml is now written into the same directory as the Bolt DB and engine files (~/.influxdbv2/) ⬆️ 2. If writing upgraded config fails, the upgrade process exits with an error instead of falling back to the HOME directory

    ⬆️ Users can use the new --v2-config-path option to override the output path for upgraded config if they can't or don't 0️⃣ want to use the default.

    v2 packaging

    📦 Based on community feedback, the v2 deb and rpm packaging has been improved to avoid confusion between versions. The package 📦 name is now influxdb2 and conflicts with any previous influxdb package (including initial 2.0.0, 2.0.1, and 2.0.2 packages). ➕ Additionally, v2 specific path defaults are now defined and helper scripts are provided for influxd upgrade and cleanup cases.

    🔋 Features

    1. 20123: Allow password to be specified as a CLI option in influx v1 auth create.
    2. 20123: Allow password to be specified as a CLI option in influx v1 auth set-password. ⬆️ 1. 20110: Allow for users to specify where V2 config should be written in influxd upgrade.
    3. 20204: Improve ID-related error messages for influx v1 dbrp commands.
    4. 20236: Delete with predicate. ⬆️ 1. 20322: Upgrade Flux to v0.99.0. ⬆️ 1. 20327: Upgrade flux-lsp-browser to v0.5.26.

    🐛 Bug Fixes

    ⬆️ 1. 20110: Use V2 directory for default V2 config path in influxd upgrade.

    1. 20137: Fix panic when writing a point with 100 tags. Thanks @foobar! 🌲 1. 20151: Don't log bodies of V1 write requests.
    2. 20097: Ensure Index.Walk fetches matching foreign keys only.
    3. 20149: Enforce max value of 2147483647 on query concurrency to avoid startup panic.
    4. 20149: Enforce max value of 2147483647 on query queue size to avoid startup panic.
    5. 20168: Auto-migrate existing DBRP mappings from old schema to avoid panic. ⚡️ 1. 20201: Optimize shard lookup in groups containing only one shard. Thanks @StoneYunZhao!
    6. 20155: Respect the --name option in influx setup whether configs already exist or not.
    7. 20155: Allow for 0 (infinite) values for --retention in influx setup. 🚀 1. 20305: Set v2 default paths and provide upgrade helper scripts in release packages