回复： I submitted an IOTDB subscription issue【 IOTDB-2766】

[gongning <27...@qq.com.INVALID>]

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"                                                                                    <sainthxd@gmail.com&gt;;
发送时间:&nbsp;2022年4月30日(星期六) 下午2:57
收件人:&nbsp;"dev"<dev@iotdb.apache.org&gt;;

主题:&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

&nbsp;黄向东
清华大学 软件学院


苏志 <273670908@qq.com.invalid&gt; 于2022年4月24日周日 14:44写道：

&gt; &amp;nbsp; &amp;nbsp; In the process of industrial production, various
&gt; environmental data such as temperature, pressure and humidity of industrial
&gt; equipment are collected by sensors. Customers are eager to detect and
&gt; notify abnormal fluctuations of sensor data in a timely manner. We hope to
&gt; calculate indicators based on the CAPABILITY of IoTDB CQ, so that
&gt; upper-layer services can subscribe to the indicator results calculated by
&gt; CQ in a timely manner, and then use the rule engine to achieve self-defined
&gt; alarm capability. For example, a steel customer wants to monitor the
&gt; abnormal fluctuation of the heating furnace in the last 15 minutes and send
&gt; an alarm.
&gt;
&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp;Now IoTDB already has CQ function, but lacks data
&gt; subscription mechanism.
&gt;
&gt; &amp;nbsp; &amp;nbsp; For example, when data is written to the IOTDB, other
&gt; systems can subscribe to the IOTDB's data, either through storage groups,
&gt; devices, measurement points, or nodes of any level。
&gt;
&gt; Command format:
&gt; 1) CREATE: CREATE SUBSCRIPTION "sub0" ON storageGroup DESTINATIONS ALL '
&gt; http://example.com:8080'
&gt; 2) Query: SHOW SUBSCRIPTIONS
&gt; 3) Delete: DROP SUBSCRIPTION
&gt;
&gt; Note:&amp;nbsp;http://example.com:8080&amp;nbsp;Service system address.
&gt;
&gt; Protocol format of IoTDB sending business system:
&gt;
&gt; ---------------------------------+
&gt; fullpathvaluetimestamp
&gt;
&gt;
&gt; ---------------------------------+
&gt; root.sg.device1.t1 82 1465839830100400200
&gt;
&gt; Influxdb Reference address:
&gt;
&gt; https://docs.influxdata.com/influxdb/v1.8/write_protocols/line_protocol_tutorial/
&gt;
&gt; https://docs.influxdata.com/influxdb/v1.8/administration/subscription-management/
&gt;
&gt;
&gt;
&gt;
&gt; Best,
&gt; ------------------------------------
&gt; gongning
&gt;
&gt;
&gt;
&gt;
&gt;
&gt; &amp;nbsp;