FETCH function interacts with the Warp 10 Storage Engine to retrieve data according to given criteria.
FETCH either accepts a list of 5 parameters or a map with the parameters. Those are defining the read access rights, the concerned Geo Time Series and the time window. Other parameters in the map input are optional.
The list input is here to keep backward compatibility with old WarpScripts. The map input allows a great flexibility, as described below.
A valid read token is needed to read data with fetch. If you use a metaset and also specify a token, the token included in the metaset will be ignored.
Concerned Geo Time Series
FETCH selects Geo Time Series according to:
selectorsparameter, which is a list of selector.
selectorsis not found,
selectorparameter which is a single selector.
selectoris not found,
FETCH begins from the newest value and stop when the oldest value is collected. Thus,
end must be defined in your request and defines the newest included value in your time window. If
end is anterior to your oldest value, the result will be empty (no Geo Time Series). The span of the time window ending at
end is then defined according to:
timespanis not defined,
FETCHcollects a maximum of
countis not defined,
startis more recent than
startare permuted internally. Both
endare included in the time window.
Since version 2.3.0, you can define boundaries around the requested data. When fetching data based on a time range, both a pre and post boundaries can be specified. When fetching by count, only a pre boundary can be requested.
Boundaries are a number of datapoints which are either before (pre boundary) or after (post boundary) the fetched data. Fetching boundaries is very useful when storing only the changes of values as they enable you to always fetch datapoints even if the requested time range does not contain any. They can also be used to fetch the first
N datapoints after a given timestamp.
Note that fetching post boundaries is less efficient than fetching the requested range or a pre boundary as the data has to be scanned in reverse order which has an impact on I/Os and ultimately on performance.
- Since version 2.3.0, you can randomly sample points with the
FETCHwill randomly return one point out of ten. This implementation is the fastest way to resample data.
- Since version 2.3.0, you can
skipthe N newest datapoints in the time window specified.
Query without looking into directory
The fetch time to read one gts among millions of gts recorded with the same classname, the same application and the same owner can take time. Use the
gts parameter to select if you exactly know the classname and all the labels.
If you want to read only Geo Time Series attributes or labels, using FIND is more efficient than fetching the last value.