Page History
...
| Metadata field | Description |
|---|---|
| etlStepMetadataFieldUUID | This UUID is used to uniquely identify a data field. |
| groupUUID | Use this UUID to identify data fields from the same input step. It is usually used in multi-input steps. |
| linkFieldUUID | This UUID identifies the source field, or the field from which a field receives data. |
| linkType | This metadata field specifies if a data field meets the following conditions:
For more information, see ETLLinkType in the API reference |
| stepIncludeField | This This should be set to false if the field is not to be outputted from the step. |
Types of Metadata Fields
There are two types of metadata fields to be considered:
| Type | Description |
|---|---|
| Default Metadata | These are all input fields available to a step and any fields which the step generates. Default metadata fields are created when input step(s) are linked to the step, or when the step is configured. These fields remain with the step even when inputs and outputs are disconnected. Default metadata enable the step to be an independent pre-configured unit. |
| Output Metadata | Fields which are actually output from a step. Output metadata fields are created when the step is first linked to an output step. These are initially identical to the default metadata fields. The user can rename, reorder and exclude fields without affecting the default metadata or the output metadata of another output, in case of multiple output steps. Output metadata fields are deleted when the link to the output step is broken. |
Field Linking
The following diagram explains how the fields are linked.
...
The highlighted link in the above diagram is a Wire wire in an Inline Step. The wire may be referenced from the Inline Step’s implementation using any of its “joints”: S1OF1, ISDF1 or ISOF1, which are the inputFieldUUID, fieldUUID (default metadata) and outputFieldUUID.
Generated fields will have only two joints: fieldUUID (default metadata) and outputFieldUUID.
...