Re:InfluxDB CTO: Why We Moved from Go to Rust
by lispisok on Sunday October 01, 2023 @03:46PM
(#37729831)
You tried to use a timeseries database without a time column?
Re:InfluxDB CTO: Why We Moved from Go to Rust
by efxhoy on Sunday October 01, 2023 @06:46PM
(#37731737)
> Don't be snarky.
https://news.ycombinator.com/newsguidelines.html
Are you expecting a real answer of how I was hoping timescale's internal watermark system would help me roll up a total count or are you just implying I'm an idiot?
Re:InfluxDB CTO: Why We Moved from Go to Rust
by mardifoufs on Sunday October 01, 2023 @07:03PM
(#37731873)
What's the difference between the watermark and a time column? Not the person you were replying to but I'm curious since I also thought that TimeseriesDB had a similar "timestamp" to influx.
Re:InfluxDB CTO: Why We Moved from Go to Rust
by efxhoy on Sunday October 01, 2023 @07:30PM
(#37732065)
TS requires you to specify a time column in each hypertable or view (continuous aggregate) where you want it to work its magic. It then stores an internal watermark that it compares to the time column in the table to figure out from where to read when refreshing.
My issue was that for a grand total I didn’t have a time column, so I couldn’t define my query as a continuous aggregate and the query had to start counting from the start of my underlying series each time.
It’s fantastic for workloads that neatly fit in the hypertable pattern though.