In the previous tutorial, you looked at the Siddhi real time data summarization capabilities by calculating the total production in the past minute.Now let's consider a more advanced scenario where you need to calculate the total value for a specific time period.
In this scenario, the foreman of the Sweet Factory needs to know the total production of Sherbet Lemon during each hour in November 2017.
It is costly to do this by recalculating the total for each and every event. What you need is a time based aggregation of the events in real time and retrieval on demand. Siddhi supports this functionality through the Incremental Aggregation concept.
Incremental Aggregation calculates the aggregated values continuously and stores them. These values can be retrieved efficiently from the store on demand. Furthermore, Incremental Aggregators support out of order event arrival with in-memory buffers for higher accuracy.
Before you begin:
In this scenario, information sent by the Sweet Bots are stored in a MySQL table named
SweetFactoryDB. You need to download and install MySQL, and create this table before you carry out the tutorial steps.
Download and install MySQL Server.
Download the MySQL JDBC driver.
Unzip the downloaded MySQL driver zipped archive, and copy the MySQL JDBC driver JAR (
mysql-connector-java-x.x.xx-bin.jar) into the
- Enter the following command in a terminal/command window, where
usernameis the username you want to use to access the databases.
mysql -u username -p
- When prompted, specify the password you are using to access the databases with the username you specified.
Add the following configuration under the Data Sources Configuration section of the
You need to change the values for the
passwordparameters to the username and password that you are using to access the MySQL database.
- To create a database table named
SweetFactoryDB, issue the following commands from the terminal.
mysql> create database SweetFactoryDB; mysql> use SweetFactoryDB; mysql> source <SP_HOME>/wso2/editor/dbscripts/metrics/mysql.sql; mysql> grant all on SweetFactoryDB.* TO [email protected] identified by "password";
Lets get started!
User Scenario 1: Defining incremental aggregation
In this scenario, lets define an incremental aggregation to calculate the total production in an incremental manner, and store the results.
Let's define an input stream as follows based on the data received from Sweet Bots. This is the same stream definition used in the previous tutorials to capture the name of the sweet category and the amount produced.
Now, let's define an aggregation for the input data. Here, you can assume that the foreman would like to know the production per hour, month and year for each sweet.
This calculates the total amount per hour, day, month and year by the arrival ime of each event. Incremental Aggregation can also be done for seconds, minutes, hours, days, months and years. However, in this sweet production scenario, aggregating by second holds no information value. Therefore, the sweet production is aggregated from hour to year.
Now, comes the question of when the production occurs. In the above aggregation, event arrival time is the time used in aggregation. The Sweet Bots send information directly from the factory floor to the server in the same network. Therefore, we can assume that the event arrival time is the production time.
If you want you can be more accurate by appending the data sent by the SweetBots to include time as shown below.
First define the input stream to include a timestamp:
Then use the timestamp for aggregation as shown below.
For this tutorial, let's continue to use the format mentioned first instead of the format in these substeps because the time differences are very slight in the hourly calculations.
This part of the aggregation specifies the following:
- From where the information to be processed is taken (i.e.,
- The value you are aggregating. In this scenario,
sum(amount) as totalAmountaggregates only the summation of values. The aggregation can also be
group byclause is optional and can be ignored if all production must be aggregated.
The completed Siddhi application looks as follows.
- Here, you have defined a stream to get information and aggregated a value for minutes-year.
- Aggregation can be stored in any type of store supported in Siddhi. For more information about the supported stores, see Configuring Event Tables to Store Data.
User Scenario 2: Retrieval of data on demand
In the previous scenario, you defined the aggregation. Now let's see how to retrieve from it. Siddhi supports this functionality through correlation of data. In this tutorial, you are retrieving data via aggregation joins. For more information on correlating data through joins see Siddhi Query Guide - Joins.
First, let's define a stream to retrieve data. The foreman needs to see the hourly production of Sherbet Lemon for November 2016. Therefore, the criteria to retrieve values are as follows.
Therefore, the input stream needs to be defined as follows:
A possible output of this retrieval is the timestamp (beginning of each hour), the name of the sweet and the total amount. Therefore, let's define an output stream with these values as follows.
In the above definition,
AGG_TIMESTAMPis the internal reference of the aggregation defining the start of the time interval.
Now, let's use the aggregation, retrieval stream, and the output stream to define data correlation from an aggregation.
Aggregation for the selected period contains aggregation for all sweets. Therefore, let's join the aggregation, and the retrieval stream based on the sweet name to filter aggregations for Sherbet Lemon.
You need to retrieve data relevant only for November 2017. Therefore, let's add it in the retrieval stream as the duration.
In the output event, the duration for which the data is retrieved must be represented in a specific format. For example, November 2017 can be represented as
2017-11-** **:**:**. The supported date formats are
<yyyy>-<MM>-<dd> <HH>:<mm>:<ss>(if time is in GMT) and
<yyyy>-<MM>-<dd> <HH>:<mm>:<ss> <Z>(if the time is not in GMT), here the ISO 8601 UTC offset must be provided for
If the user needs a specific time duration, the query must be changed as follows. Both durations specified must adhere to the data formats required by Siddhi.
intervalfor the retrieval to specify for which intervals you want the data to be retrieved.
Interval can be in the format of
YEARS( these values are not case sensitive).
The completed statement including the output stream looks as follows:
In the above definition,
a.AGG_TIMESTAMPis the internal data of the aggregation defining the start of the time interval. For instance, in the November 2017 duration, there is a 24*30 hourly production aggregation. The first output event has the timestamp of the date and time of
1st November 2017 00:00:00.
The completed Siddhi application with the possible sink and source configurations is as follows.