Transcript Process and order to generate the Aggregates Issue: the red dashed-line arrows’ processes Deliveries 5.1 Averages and means hour P1Y day P1Y-dx-avg week winter-avg fortnight month quarter year var summer-avg Process this group at the same time P1Y-WA-avg 3 Calculation.

Process and order to generate the Aggregates
Issue: the red dashed-line arrows’ processes
Deliveries
5.1 Averages and means
hour
P1Y
day
P1Y-dx-avg
week
winter-avg
fortnight
month
quarter
year
var
summer-avg
Process this
group at the
same time
P1Y-WA-avg
3 Calculation of base aggregations
P1D
P8H-run
P8H-dmax
The issue is generated by these reasons:
•
•
•
Two input data (hour and day)
Generation of same output aggregate, separately
The rule not to generate the aggregates again (checking if
there is any updated data) are excluding the data the
following calculation of the agg (see example below)
Example:
Deliveries
All data
inserted/updated:
2015/05/24
hour
(years: 2013, 2014)
day
(years: 2011, 2012)
Generate the agg. at 10:00 of the day 2015/05/25
Bassed on ‘hour’
P1Y
P1Y
Check data
to generate
Result
Mean of
Generated [resulttime]
2013
2015/05/25 10:00
2014
2015/05/25 10:00
Check data
to generate
Do we have data inserted/updated after the last
generation of the aggregate?
data of type ‘day’ inserted/updated >= resultime of the agg. ‘P1Y’
2015/05/24 >= 2015/05/25 10:00 ?? is false so do not generate.
For this reason the data didn’t get
processed the second time with the
other type