The influxdb migration page does not explain buckets vs buckets, tags vs symbols and so on. We should make something similar to what influx3 has to explain migrating from influx2.
Also, when we do this, we can change the current sparse table example to do it using a matview and using TTL on the original table, which probably makes sense.
The influxdb migration page does not explain buckets vs buckets, tags vs symbols and so on. We should make something similar to what influx3 has to explain migrating from influx2.
Also, when we do this, we can change the current sparse table example to do it using a matview and using TTL on the original table, which probably makes sense.