PowerExchange for Kudu User Guide

PowerExchange for Kudu User Guide

Kudu Dynamic Mapping Overview

Kudu Dynamic Mapping Overview

You can use Kudu data objects as dynamic targets in a mapping.
Use the Kudu dynamic mapping to accommodate changes to target and transformation logics at run time. You can use a Kudu dynamic mapping to manage frequent schema or metadata changes or to reuse the mapping logic for data sources with different schemas. Configure rules, parameters, and general transformation properties to create the dynamic mapping.
If the data source for a target changes, you can configure a mapping to dynamically get metadata changes at runtime. If a target changes, you can configure the Write transformation to accommodate changes to the target.
You do not need to manually synchronize the data object and update each transformation before you run the mapping again. The Data Integration Service dynamically determine transformation ports, transformation logic in the ports, and the port links within the mapping.
There are the two options available to enable a mapping to run dynamically. You can select one of the following options to enable the dynamic mapping:
  • In the
    Data Object
    tab of the data object write operation, select the
    At runtime, get data object columns from data source
    option when you create a mapping.
    When you enable the dynamic mapping using this option, you can refresh the target schemas at the runtime.
  • In the
    Ports
    tab of the data object write operation, select the value of the
    Columns defined by
    property as
    Mapping Flow
    when you configure the data object write operation properties.
For information about dynamic mappings, see the
Informatica Developer Mapping Guide
.

0 COMMENTS

We’d like to hear from you!