Script result: Streaming
StackState Self-hosted v5.0.x
This page describes StackState version 5.0.
Most API functions execute asynchronously. That means they will not directly return results. Some functions are dependent on the network or other resources in order to complete, therefore they cannot immediately return results. Such asynchronous functions return an AsyncScriptResult
. On top of that, some APIs can deal with large amounts of data, in which case we do not want to process all the data at once. Such APIs return a StreamingScriptResult
, which allows for the result to be processed one element at a time.
Working with StreamingScriptResult.then
StreamingScriptResult.then
If the result of your script is returned as a StreamingScriptResult
, StackState will produce an asynchronously executed stream of data. If you want to further process the data in the StreamingScriptResult
, the .then
method can be used.
The .then
method expects a Groovy closure /(groovy-lang.org/). The closure will be executed for each element in the StreamingScriptResult
. This lambda function can work with the element and returns a new list of items or a single new item.
For example:
The Groovy script above can be shortened to:
The it
keyword is a default Groovy keyword that means you do not need to define a variable in which you receive your result. You might see this being used in our examples.
Chaining
To avoid computations becoming too heavy, the StreamingScriptResult
cannot be chained with either AsyncScriptResult
or StreamingScriptResult
itself.
Collecting results
The StreamingScriptResult
can be returned from a script, after which the script runtime will take care of collecting the results. This is the preferred way of using the StreamingScriptResult
because it allows StackState to process data incrementally with constant memory. In exceptional cases, it can be useful to actually run a stream, such that all results are accessible. This can be achieved with the collectStream
function.
Be careful collecting data from a stream with higher limits. This can cause memory pressure and the script to fail. It is always best not to collect the data and process the data in a streaming fashion.
For example:
Will result in an AsyncScriptResult with the streamed items in a list. If the limit is exceeded, the execution will fail. To avoid failing if the limit is reached, but still produce the maximum amount of results, collectStream takes a second parameter:
See also
Last updated