It creates a new datacube by splitting input fragments in nsplit output fragments in the same origin database.
- cube: name of the input datacube. The name must be in PID format.
- schedule: scheduling algorithm. The only possible value is 0, for a static linear block distribution of resources.
- nsplit: number of output fragments per input fragment. If the number of tuples in input fragment is not a multiple of nsplit, output fragments will have a different number of tuples.
- container: name of the container to be used to store the output cube; by default, it is the input container.
- description: additional description to be associated with the output cube.
- exec_mode: operator execution mode. Possible values are async (default) for asynchronous mode, sync for synchronous mode with json-compliant output.
- ncores: number of parallel processes to be used (min. 1).
- nthreads: number of parallel threads per process to be used (min. 1).
- sessionid: session identifier used server-side to manage sessions and jobs. Usually, users don’t need to use/modify it, except when it is necessary to create a new session or switch to another one.
- objkey_filter: filter on the output of the operator written to file (default=all => no filter, none => no output, split => shows operator’s output PID as text).
Split the datacube identified by the PID “URL/1/1”:
[OPH_TERM] >> oph_split cube=URL/1/1;nsplit=2;