Hacker News new | past | comments | ask | show | jobs | submit login

I tried out InfluxDB a while ago in my spare time and was intrigued by the feature set, but ultimately couldn't get past the abstruse query language, especially coming from the simpler and more flexible PromQL (not being able to do ad-hoc math across time series was a big deal for my use case). I'm eagerly looking forward to giving it another shot with Flux and have super-high hopes.

What does the data model for time series look like in 2.0? Mostly the same as 1.x, or has that gotten more flexible as well?




For now we take writes in the 1.x line protocol so it’s still measurement, tags, and field. However, Flux doesn’t really make that a requirement. So in the future we plan on having a way to write series in without requiring a field or even a measurement.

Once the planner gets the data to the Flux processing engine it views everything thing as a table of data with columns and records. So it’s much more flexible in how we can represent data.


Sounds good; thanks for the reply!


FYI, the article mentions that InfluxDB will eventually support PromQL:

> With InfluxDB 2.0 we support both push and pull models out of the box. Eventually we’ll also support querying via PromQL out of the box




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: