Re: Documentation on the use of triggers
Hi Ning, Thanks for your contribution! The PR looks good to me, I have merged it. Steve Su 苏志 <273670...@qq.com.invalid> 于2022年5月1日周日 23:23写道： > > The following shows the SQL syntax of registering a trigger. > > CREATE TRIGGER (BEFORE | AFTER) INSERT ON a globally unique ID of the trigger, which is case sensitive. At present, the > trigger can listen to all data insertion operations on the time series. The > hook can be called BEFORE or AFTER the data is inserted. FULL-PATH can be a > time-series (measurement) path such as root.sg1.d1.s1, a device path such as > root.sg1.d1, a storage group path such as root.sg1, or even a non-measurement > path with business semantic such as root.sg1.x. CLASSNAME is the full class > name of the trigger. Note > CLASSNAME, KEY and VALUE in the attributes need to be quoted in single or > double quotes. > > Only one trigger can be registered per full-path. > > When multiple prefix paths of a path are registered with triggers, for > example, trigger trigger-sg1d1s1 is registed on root.sg1.d1, trigger > trigger-sg1d1 is registed on root.sg1.d1, and trigger trigger-sg1 is registed > on root.sg1. When inserting data to root.sg1.d1.s1, triggers will be > triggered in the following order: trigger-sg1d1s1 -> trigger-sg1d1 -> > trigger-sg1. > > Best, > > gongning
?????? 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: http://example.com:8080 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 > > > > > >
Documentation on the use of triggers
The following shows the SQL syntax of registering a trigger. CREATE TRIGGER
[BUILD-UNSTABLE]: Job 'IoTDB/IoTDB-Pipe/master [master] [578]'
BUILD-UNSTABLE: Job 'IoTDB/IoTDB-Pipe/master [master] [578]': Check console output at "https://ci-builds.apache.org/job/IoTDB/job/IoTDB-Pipe/job/master/578/";>IoTDB/IoTDB-Pipe/master [master] [578]"
