Loading

DELETE

gts
Configuration parameters

The DELETE function is used to delete a set of GTS from a Warp 10 platform. A delete endpoint must be set on the Warp 10 configuration.

Delete expects 5 parameters on top of the stack: the write token of the Warp 10 application, a string corresponding to a gts selector, a start and a end timestamp and finally the number of GTS expected to be deleted.

For safety reasons DELETE will first perform a dryrun call to the /delete endpoint to retrieve the number of GTS which would be deleted by the call. If this number is above the expected number provided by the user the actual delete will not be performed and instead an error will be raised.

Delete will push as a result the number of GTS really deleted.

If both end_timestamp and start_timestamp are NULL, Warp 10 will perform a delete all. FETCH won't find anything after a delete all.

Since 2.7.3, when setting NULL as the number of GTSs to delete, the DELETE function runs in dry mode. This means no GTS is deleted and the function returns the GTSs list that would be considered by the DELETE.

DELETE is available since version 1.0.5.

Signatures

Examples

// Write token 'TOKEN' // Gts selector 'gts.to.delete{}' // Start Timestamp 1479372838011043 // End timestamp NOW // DELETE expects a count number (if nb GTS > count, DELETE is stopped) 1 DELETE