Release Announcement: InfluxDB OSS 2.2.0
Sam Dillard /
Apr 07, 2022
OSS data remote replication, security enhancements, and improvements in Flux available now.
We’ve been busy bringing the latest improvements to this release. Some of these have been available within InfluxDB Cloud, and now we are pleased to offer them within the open source offering for those of you developing against the OSS edition on your laptop or deploying this at the edge.
- InfluxDB 2.2.0 – release notes
This release includes the following new features:
- Technical Preview: OSS to Cloud data replication
- Flux advancement
OSS to Cloud data replication
Replication between remote buckets was introduced in this version. A bucket in OSS can be configured to replicate to a bucket in a remote service. This is a critical capability in topologies combining edge and cloud deployments of InfluxDB.
This feature is noted as a “technical preview” because it is not yet intended for production use. It is not listed as “experimental” because it is planned as an officially supported feature.
Private IP Validation for Flux and Template Fetching
Template fetching and some Flux functions make HTTP requests over the network. This feature’s optional configuration can limit InfluxDB’s access to private IPs and therefore the possibility of Server Side Request Forgery (SSRF) attacks. By default, private IPs are still reachable, so there is no breaking change. They can be made inaccessible by invoking the new
Flux was upgraded from 0.139.0 to 0.161.0. This includes the following features and enhancements:
- Added new experimental
http/requestspackage which increases flexibility of Flux to make HTTP calls and use their response data.
isType()function. This convenience function will allow Flux to check types of columns which will help dynamically apply mathematical operations on a set of Fields that may contain non-numeric Fields.
display()function. This is like a
- Various enhancements to
- Added vectorization to applicable functions like
- Continued performance enhancements (i.e.,
sort() |> limit())
mqtt.publish()to reuse TCP connections when being called in a loop. This allows for functions like
mqtt.publish()on each row of a table stream without re-establishing the handshake for each record.
If all of that feature advancement isn’t enough, there are a handful of bug fixes which also have been addressed. Check out the release notes for all the details or if you are looking for a specific fix.