Hi, IMO, the CQ (continuous query) is for calculating and transforming data. Users can do it by reading data from IoTDB and then writing data back. The point is, is there an enhancement to doing that in IoTDB internally? (The only thing is saving the network bandwidth up to now.)
IoTDB will support Trigger quickly (Yurong Su is working on that), and it allows doing anything that you want to do when a data point comes. Users can implement CQ (continuous query) easily by using the trigger feature. And I think once we find that implement the CQs separately can bring more benefit, we will implement it asap. Of course, we welcome everyone who wants to contribute to a native CQ feature to IoTDB :D Best, ----------------------------------- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 TianFeng <[email protected]> 于2020年11月23日周一 上午11:42写道： > Hi > Will there be a continuous query function similar to infixdb > in the future, which can be used to reduce frequency to store historical > data?
