-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
Note: I may do a better write-up of this task in the future.
JARVIS uses InfluxDB OSS v2 for its database. Recently, InfluxDB 3 Core launched. v3 is architecturally different than v2, not just a direct upgrade, so we need to do some research and decide whether to stick with v2 or switch to v3.
Here is the documentation for both versions:
InfluxDB 3 Core
InfluxDB OSS v2
This research is open-ended, but some good things to find out would be:
- Would v3 work well with our timestamped telemetry?
- What changes would need to be made to the code if we switched?
- Does InfluxData recommend a specific version for stability or long-term support?
One thing I immediately noticed, for example, is that v3 allows using either SQL or InfluxQL for the query language, whereas v2 requires using Flux. This may be a benefit for v3, as SQL is more common in industry and we may have members who have experience in it or wish to learn it.
Reactions are currently unavailable