Introduction on Expiry time
One of the most important concepts of Delft-FEWS is that always the latest forecast data is available to be used. In a typical operational Delft-FEWS forecasting system, new data is constantly imported, while older data is no longer relevant and can be removed. For a lot of database tables in fews master-controller database, the rows (records) in the database have a expiryTime column specifying when the data can be removed. The removal is done by the so-called RollingBarrel process. It will remove any data for which the expiry time is exceeded.
GlobalProperties EXPIRY_DAYS
The global property EXPIRY_DAYS (default 10 days) is a global property that controls the default expiration time for new forecast data that is stored in the Delft-FEWS database.
Expiry time for TimeSeries and ImportStatus
The expiryTime value in the TimeSeriesSet configuration of a TimeSeriesImport overrides DEFAULT_EXPIRY_DAYS setting for the expiry time of TimeSeries and ImportStatus.
Expiry time for thresholdEvents
The expiryTime value of thresholdEvents is the maximum of 100 days and the DEFAULT_EXPIRY_DAYS setting.
Expiry time for other types of records
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.
