...
The System default expiry time for forecast data in Delft-FEWS is 10 days. The system default can be altered by specifying a global property, e.g. DEFAULT_EXPIRY_DAYS=30
Code Block language xml DEFAULT_EXPIRY_DAYS=30
Import workflows can have expiry time in general section, will be used for all imported time series
Code Block language xml <expiryTime unit="day" multiplier="365"/>
Import, Transformation, General Adapter, .. modules can have expiry times in timeSeriesSet element, e.g.
Code Block language xml <expiryTime unit="day" multiplier="2"/>
The expiryTime value in the TimeSeriesSet configuration of a TimeSeriesImport overrides DEFAULT_EXPIRY_DAYS setting for the expiry time of TimeSeries and ImportStatus. If an expiryTime is defined at the TimeSeriesSet level, the time series blobs will get this expiry time, no matter what the workflow says.
If the timeseries is of an external type, the timeseries will also stay accessible. If a time series is of the simulated type, data access has to go through a query where the taskrun record plays a major role. This taskrun record expirytime is defined by the workflow.
| Tip | ||
|---|---|---|
| ||
When expiryTime of many TimeSeriesSets are conceptually related, it is recommended to explicitely set these using a globalProperty variable using tags. |
Guidelines for setting expiry times
...
This setting overrides the expiry time of the taskrun and everything attached to it. The ‘runExpiryTime’ applies only to forecast runs, so only to time series created in a forecast run. Imported time series (external historicals or external forecasts) are not connected to a particular workflow run, so ‘runExpiryTime’ will not work for imported timeseries.
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. If an expiryTime is defined at the TimeSeriesSet level, the time series blobs will get this expiry time, no matter what the workflow says.
If the timeseries is of an external type, the timeseries will also stay accessible. If a time series is of the simulated type, data access has to go through a query where the taskrun record plays a major role. This taskrun record expirytime is defined by the workflow. If the taskrun record is removed, the simulated data has become orphan as it has become inaccessible.
...
| title | Use globalProperties for controlling expiryTime timeSeriesSets... |
|---|
.
Expiry time for thresholdEvents
...