OPH_MERGE¶

Description¶

Type

Data Process.

Behaviour

It creates a new datacube grouping nmerge input fragments in a new output fragment. If the number of fragments of the input datacube is not a multiple of nmerge, then there will be some output fragments grouping a number of fragments lower than nmerge. In addition, the number of tuples in each output fragment is generally different.

Parameters

• 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.
• nmerge: number of input fragments to merge in an output fragment. In order to merge all fragments, it can be used the default value “0”.
• 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.

System parameters

• 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).
• 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, merge => shows operator’s output PID as text).

Examples

Merge groups of 2 fragments of the input data cube identified by the PID “URL/1/1” together:

[OPH_TERM] >>  oph_merge cube=URL/1/1;nmerge=2;

Arguments¶