You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@community.apache.org by "Xiangdong Huang (Jira)" <ji...@apache.org> on 2020/02/25 03:00:00 UTC

[jira] [Closed] (COMDEV-355) Apache IoTDB trigger module for streaming cumputing

     [ https://issues.apache.org/jira/browse/COMDEV-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Xiangdong Huang closed COMDEV-355.
----------------------------------
    Resolution: Invalid

According to [1], I should open this issue on IoTDB Jira track. So I close this issue here.

[1] [http://community.apache.org/guide-to-being-a-mentor.html]

> Apache IoTDB trigger module for streaming cumputing
> ---------------------------------------------------
>
>                 Key: COMDEV-355
>                 URL: https://issues.apache.org/jira/browse/COMDEV-355
>             Project: Community Development
>          Issue Type: Wish
>          Components: GSoC/Mentoring ideas
>            Reporter: Xiangdong Huang
>            Priority: Major
>              Labels: IoTDB, gsoc2020
>
> IoTDB is a time-series data management system and the data usually comes in a streaming way.
> In the IoT area, when a data point comes, a trigger can be called because of the following scenario:
>  * (single data point calculation) the data point is an outlier point, or the data value reaches a warning threshold. IoTDB needs to publish the data point to those who subscribed the event.
>  * (multiply time series data point calculation) a device sends several metrics data to IoTDB, e.g., vehicle d1 sends average speed and running time to IoTDB. Then users may want to get the mileage of the vehicle (speed x time). IoTDB needs to calculate the result and save it to another time series.
>  * (Time window calculation) a device reports its temperature every second. Though the temperature is not too high, if it keeps increasing in 5 seconds, IoTDB needs to report the event to those who subscribe that.
>  
> As there are many streaming computing projects already, we can integrate one of them into IoTDB.
>  * If IoTDB runs on Edge, we can integrate Apache StreamPipes or Apache Edgent.
>  * If IOTDB runs on a Server, the above also works  and Apache Flink is also a good choice.
> The process is:
>  * User registers a trigger into IoTDB.
>  * When a data comes, IoTDB save it and check whether there are triggers on it
>  ** If so, call a streaming computing framework to do something;
>  
> You may need to know:
>  * At least one streaming computing project.
>  * SQL parser or some other DSL parser tool.
> You have to modify the source codes of IoTDB server engine module.
> Difficulty: A little hard
> mentors:
> hxd@apache.org
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@community.apache.org
For additional commands, e-mail: dev-help@community.apache.org