Our first feature rich release following 2.0 is out. Discover what we have packed into release 2.1 and how some of these features now probably make Warp 10™ also the fastest timeseries database!
This release could almost have been a major one given how many changes it includes, but we decided to remain on the 2.x path, after all 2.1 is one twentieth of 42!
Discover a list of features and enhancements added to 2.1. We highly encourage you to migrate to 2.1 to benefit from all of them, performance improvements make the move way worth it.
|Discover the latest version of Warp 10.|
All the external HTTP endpoints (ingress, egress, plasma) can now be configured with SSL support enabled. This requires that you have a certificate and associated private key available in a Java Key Store. You can use separate JKS and certificates for each endpoint.
Geo Time Series can contain LONG, DOUBLE, BOOLEAN or STRING values. With release 2.1, STRING values can now either be standard UTF-8 encoded strings or ISO-8859-1 representations of raw byte arrays, we call this subtype BINARY. Encoding binary data in base64 is no longer required, thus leading to a 25% reduction of the storage space required for blobs. The
->GTS functions have been modified to correctly return data that was stored as binary.
The support of binary values enabled the automatic encoding of multivariate values. This new type of values enables Warp 10 to reach tremendous levels in terms of performance. This is the addition which made our record breaking Raspberry Pi 4 benchmark possible.
We have modified the configuration mechanism for Warp 10 to support multiple configuration files. This makes it easier to store the configuration for a given extension in its own file, for example and allows for an overall better organization of your config.
We have enhanced the datalog mechanism to support forwarding to multiple targets from within a single Warp 10 instance, and to support sharding the dataset across targets. Coupled with a dedicated extension, you can configure a set of standalone Warp 10 instances to act as a mini-cluster, ensuring high availability (datalog replication) and scalability (sharding).
We retired the aging quantum web interface to Warp 10 has been, and we replaced with a richer, less buggy and more performant web app dubbed Warp Studio. Warp Studio is also accessible online.
Release 2.1 has a certain number of new functions which were added in different domains to make you more efficient when working with WarpScript.
The set of operators working on Geo Time Series has been expanded and now includes comparison operators
!=, bitwise operators
| (OR) and
^ (XOR) and boolean operators
| (OR) and
Function to produce a summary of the Warp 10 instance configuration and status, useful when reporting a problem:
Handy function to shuffle a list:
->LONGBYTES to convert LONGs to byte arrays.
Macros can now be executed from registers via an enhanced
Lastly, many functions operating on Geo Time Series can now also operate on Encoders.
Bug fixes and code refactoring have made some operations way faster. As an example,
FILTER are now faster when called on several 10s of thousands of GTS. Also, all
BUCKETIZE operations following a FETCH should see performance improvements and MAP operations were sped up thanks to faster subseries extraction.
On the storage engine side, the support for multiple values in the input format enables blazing-fast ingestion performance even on very limited hardware. A future blog post will show how this probably makes Warp 10 also the fastest time series platform!
How to migrate an existing Warp 10 instance to 2.1?
The 2.1 release of Warp 10 is compatible with previous releases, but slight changes to the layout of the configuration files requires that you proceed with the steps below. The configuration change is that Warp 10 can now use multiple configuration files sitting in the
etc/conf.d directory, this enables you to create separate configuration files for separate components of Warp 10, thus making the configuration easier to read. This also makes it possible for the WarpFleet packages and plugins to have their own separate configuration file.
- Get the latest version of Warp 10: https://www.warp10.io/download
- Extract the jar (ie:
warp10-2.1.0.jar) from the archive
- Extract the
warp10-standalone.shfile from the archive
- Stop your current Warp 10 instance:
- Copy the new jar and new
warp10-standalone.shin your previous Warp 10
- Adjust Java Heap size if needed
- Create a new directory
- Move old configuration file to this new directory
- Start your new Warp 10 instance:
Co-Founder & Chief Technology Officer