Node connection

Edges connecting nodes in a pipeline determine which direction data flows and which node leads to which node. A well-designed connection ensures that data flows in one direction, from the source through the processing steps to the final destination.

Create edge (connection)

Connections between nodes are made by dragging from the output connection point to the input connection point.

1. Hover the mouse over the right connection point (output port) of the preceding node (Upstream).
2. Once the connection point is activated, press and drag.
3. Place it on the left connection point (input port) of the following node (Downstream).
4. An edge is created and data flow between the two nodes is established.

Data flow rules

The following rules apply to connections between nodes: Entity / Relation nodes operate as source/sink in the same way as datasets.

Connections allowed

departure node	arrival node	data flow
Dataset / Entity / Relation →	Code	Reading data as input to a code node
Code →	Dataset / Entity / Relation	Write processing results of code node
Code →	Code	Pass intermediate processing results to the next code node

Creating a connection does not guarantee execution

The editor does not automatically block direct dataset-to-dataset connections, connections between an event step and a dataset, or cyclic connections. A visible edge alone does not guarantee an executable configuration. Place a code node between data transformations and design the pipeline as a one-way acyclic graph. See Pipeline errors to review execution results and step errors.

Input/output binding

When you connect a Code node and a Dataset / Entity / Relation node, the input/output connection information (binding) is recorded in the Options tab of the code node. (It does not compare schema types and automatically pair them, but registers the connections themselves as input and output.)

On the Options tab, specify the following for each binding:

• Reading Mode (Input): Incremental / Full
• Write mode (output): Append / Overwrite / Upsert

Step Options

At the top of the Options tab, the Step Options JSON field is always displayed, independent of the input/output bindings. Any code node can be used at any time, even without a dataset connection. The JSON object entered here is passed to the step as options when executed, and can be read as run(options=...) in the code.

• The value must be a JSON object. If the format is incorrect, an error will be displayed and the file will not be saved.
• If you leave the field blank or {}, it will run without step options.

Reuse of existing resources and duplicate names

You can directly select and connect already created datasets, entities, and relationships using the input/output selector in the Options tab. At this time, if there is already a node of the same type and name in the pipeline, the Save as new name window opens. This is because within one pipeline, there cannot be more than one node of the same type with overlapping names (the name is a table identifier).

• The window is pre-suggested a new name that does not overlap (e.g. orders → orders_copy).
• Check the name and duplicate it will leave the original intact and create a copy with the new name to continue this connection.
• The name must start with a lowercase letter, and only lowercase letters, numbers, and underscores can be used.

Multiple input/output

You can connect multiple Dataset nodes to one Code node.

Multiple input example

• Connect multiple datasets as input to one Code node to perform join and merge processing.
• Each input is referenced as a separate variable within the Code node.

Multiple output example

• From one Code node, results can be distributed to multiple datasets according to conditions.

Edge Management

Delete connection

• Click the × button that appears when you hover your mouse over the connection line (Edge) to immediately remove it.

Change connection

To change an existing connection to another node:

1. Delete the existing connection.
2. Reconnect to the new target node.

Check connection status

You can see all input/output connections in the Options tab of the code node.

Item	Description
Inputs	Sources that provide data to the current code node and read mode (incremental/full)
Outputs	What receives the results of the current code node and the write mode (append/overwrite/merge)