?????? I submitted an IOTDB subscription issue?? IOTDB-2766??
Hi?? The function of data subscription based on trigger implementation is not very convenient for users to use, and the current trigger does not support clustering. I have discussed the design idea of subscription with Yurong for several times before, and I will discuss it later to form a design document, and finally realize the subscription function together with my partners. Best, gongning ---- ??: "dev" http://example.com:8080' 2) Query: SHOW SUBSCRIPTIONS 3) Delete: DROP SUBSCRIPTION Note:nbsp;http://example.com:8080nbsp;Service system address. Protocol format of IoTDB sending business system: -+ fullpathvaluetimestamp -+ root.sg.device1.t1 82 1465839830100400200 Influxdb Reference address: https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/ https://docs.influxdata.com/influxdb/v1.8/administration/subscription-management/ Best, gongning nbsp;
Re: I submitted an IOTDB subscription issue【 IOTDB-2766】
Hi, Any idea to implement? Can the trigger module support this? (but iotdb does not support too many trigger now, I think) Does Yurong have any idea? Best, --- Xiangdong Huang School of Software, Tsinghua University 黄向东 清华大学 软件学院 苏志 <273670...@qq.com.invalid> 于2022年4月24日周日 14:44写道： > In the process of industrial production, various > environmental data such as temperature, pressure and humidity of industrial > equipment are collected by sensors. Customers are eager to detect and > notify abnormal fluctuations of sensor data in a timely manner. We hope to > calculate indicators based on the CAPABILITY of IoTDB CQ, so that > upper-layer services can subscribe to the indicator results calculated by > CQ in a timely manner, and then use the rule engine to achieve self-defined > alarm capability. For example, a steel customer wants to monitor the > abnormal fluctuation of the heating furnace in the last 15 minutes and send > an alarm. > > Now IoTDB already has CQ function, but lacks data > subscription mechanism. > > For example, when data is written to the IOTDB, other > systems can subscribe to the IOTDB's data, either through storage groups, > devices, measurement points, or nodes of any level。 > > Command format: > 1) CREATE: CREATE SUBSCRIPTION "sub0" ON storageGroup DESTINATIONS ALL ' > http://example.com:8080' > 2) Query: SHOW SUBSCRIPTIONS > 3) Delete: DROP SUBSCRIPTION > > Note:http://example.com:8080Service system address. > > Protocol format of IoTDB sending business system: > > -+ > fullpathvaluetimestamp > > > -+ > root.sg.device1.t1 82 1465839830100400200 > > Influxdb Reference address: > > https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/ > > https://docs.influxdata.com/influxdb/v1.8/administration/subscription-management/ > > > > > Best, > > gongning > > > > > >
I submitted an IOTDB subscription issue?? IOTDB-2766??
In the process of industrial production, various environmental data such as temperature, pressure and humidity of industrial equipment are collected by sensors. Customers are eager to detect and notify abnormal fluctuations of sensor data in a timely manner. We hope to calculate indicators based on the CAPABILITY of IoTDB CQ, so that upper-layer services can subscribe to the indicator results calculated by CQ in a timely manner, and then use the rule engine to achieve self-defined alarm capability. For example, a steel customer wants to monitor the abnormal fluctuation of the heating furnace in the last 15 minutes and send an alarm. Now IoTDB already has CQ function, but lacks data subscription mechanism. For example, when data is written to the IOTDB, other systems can subscribe to the IOTDB's data, either through storage groups, devices, measurement points, or nodes of any level?? Command format: 1) CREATE: CREATE SUBSCRIPTION "sub0" ON storageGroup DESTINATIONS ALL 'http://example.com:8080' 2) Query: SHOW SUBSCRIPTIONS 3) Delete: DROP SUBSCRIPTION Note:http://example.com:8080Service system address. Protocol format of IoTDB sending business system: -+ fullpathvaluetimestamp -+ root.sg.device1.t1 82 1465839830100400200 Influxdb Reference address: https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/ https://docs.influxdata.com/influxdb/v1.8/administration/subscription-management/ Best, gongning
