MDI

Overview of Metadata Injection ..

In this Workshop, you will:

• Create a number of transformations that prepare the metadata and inject these specific values through the ETL Metadata Injection step.

Metadata is traditionally defined and configured at design time, in a process known as hard coding, because it does not change at run time.

In this scenario, onboarding the files would require a CSV file input step for each of the different delimiters.

hard coded values in ktr
  1. Double-click on the CSV File Input steps to display the metadata properties:

~/How-To--Metadata-Injection/Overview of Metadata Injection/file_hard_coded.ktr

hard coded values

Each data source requires its own workflow.

The challenge becomes to find a way to dynamically inject the required metadata properties at run time via a template.


Metadata Properties

Steps in a Transformation are configured with associated metadata property values, e.g. step name, filename, delimiter, and so on ..

These metadata properties are saved as .ktr=xml

A neat way to introduce metadata injection is to change a metadata property in the xml of a step.

  1. Copy / Paste the step into Visual Studio Code:

csv input step xml
  1. Change a metadata property: <name>Whatever</name>

  2. Copy / Paste xml into a new transformation:

Each of the Step 'settings' are defined in the .xml. By changing the step name, you've manually 'injected' a new value.

Last updated

Was this helpful?