...
| Tip | ||
|---|---|---|
| ||
When expiryTime of many TimeSeriesSets are conceptually related, it is recommended to explicitely set these using a globalProperty variable using tags. |
Preserving taskrun information for access to timeseries (before 2017.01)
Timeseries in the database without taskruns are referred to as "orphaned timeseries". Since 2017.01, taskruns for new timeseries are preserved until the timeseries expire, and therefore the newly created timeseries cannot become orphaned anymore. Note that simulated timeseries are not meaningful without taskrun information and should never be orphaned. Only external timeseries can be orphaned, but without taskruns they can not be amalgamated (merged) any more. In order to preserve taskruns longer than the default of ten days, the taskruns expirytime should be increased. See also ImportAmalgamate for more information on amalgamate.
Expiry time for thresholdEvents
...
<eventCode id="Comms"><expiryTime unit="day" multiplier="10"/></eventCode>
MCRolling barrel extends expiry times for SystemActivities, Tasks and TaskRuns when necessary (2017.01 and later)
The MC RollingBarrel component will extend the expiryTime of system activities and tasks when the rows are almost expired and there is still forecast data attached.
Expiry time for records generated by the master-controller (2017.01 and before)
The master-controller configuration defines the following section section in the fews.master.mc.conf configuration file.
<rollingbarrel>
<taskruns expiredays="10"/>
<logentries expiredays="5"/>
<reports expiredays="5"/>
<default expiredays="10"/>
</rollingbarrel>
These settings are used by master-controller components when creating records. The taskruns expiry time used is read from the taskproperties, when missing the above setting is used.
An edit of a task in the Admin Interface will update the taskproperties.xml to the value in <taskruns expiredays="..."/> setting.