Launch a task graph from a given terminal node in the task graph
Source:R/manual_layer_node.R
compute.RdThe task graph is implicitly defined by various delayed objects having others
in their argument lists.
Usage
compute(
node,
timeout_seconds = NULL,
verbose = FALSE,
namespace = NULL,
force_all_local = FALSE
)Arguments
- node
The object whose args are being set – nominally, produced by
delayed,delayed_generic_udf, etc.- timeout_seconds
Number of seconds after which to stop waiting for results. Note that in-flight computationsa are not cancelled; this is not supported by the underlying R package we use for concurrency.
- verbose
If supplied, show the DAG state at the start and end, along with all node start/end. Also shown are any stdout prints from the individual nodes, but these are only visible once the compute node has completed.
- namespace
The namespace to charge for any cloud costs during the execution of the task graph. This can be null only when all nodes have
local, or whencomputeis called withforce_all_local.- force_all_local
While individual nodes can be marked with
local=TRUEto not be executed on TileDB cloud, this flag overrides the defaultlocal=FALSEfor *all* nodes in the task graph.
See also
Other manual-layer functions:
array_info(),
compute_sequentially(),
delayed_args<-(),
delayed_args(),
delayed_array_udf(),
delayed_generic_udf(),
delayed_sql(),
delayed(),
deregister_array(),
deregister_group(),
deregister_udf(),
execute_array_udf(),
execute_generic_udf(),
execute_multi_array_udf(),
execute_sql_query(),
get_udf_info(),
group_info(),
list_arrays(),
list_groups(),
login(),
register_array(),
register_udf(),
update_udf_info(),
user_profile()