Hi, sorry to be so unspecific. Prometheus has quite a nice Documentation as reference [1].
Thinks I like there are for example: Math on Timeseries: * timeseriesA +(, -, *, /) timeseriesB as a new series Reuse Aggregations as new timeseries: Avg(timeseriesA)/avg(timeseriesB) in a group by context Best Julian [1] https://prometheus.io/docs/prometheus/latest/querying/basics/ Von: Xiangdong Huang <[email protected]> Datum: Dienstag, 23. Februar 2021 um 09:51 An: dev <[email protected]> Betreff: Re: Do we need a new Query Engine? Hi, Welcome to more discussion about this topic. > I really love there is the power of their query language. Lots of functions and the possibility to do math on timeseries Sharing some examples may be the first step to open our mind :D Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 Julian Feinauer <[email protected]> 于2021年2月23日周二 上午4:36写道： > Hi folks, > > the title is a bit drastic but what I wanted to bring up as a discussion > is what we plan to allow in our Query Language. > > I worked a bit with Prometheus recently and what I really love there is > the power of their query language. Lots of functions and the possibility to > do math on timeseries. So not only scalar and timeseries but also > timeseries and timeseries. > > When I though about how to integrate that seamlessly into IoTDB I > questioned myself if the current state of the “Query Engine” or “Execution > Engine” is setup right for that or if there would be the need to “rewrite” > it. > My gut feeling is that it started off well and just grew over and over > with many more features and branches for all the different options. > > What are other peoples feelings? > I really would love to have some more powerful math! > > Julian >
