At a minimum, a property mapper requires both a record source and a dimension source to define the components that will supply it with record and dimension data.
You can leave the other settings at their defaults while developing your initial working pipeline.
To add a property mapper:
The Property Mapper editor appears.
In the Name text box, type a unique name for this property mapper.
In the Sources tab, set the record source and dimension source.
Click Mappings to open the Mappings editor, where you can view and modify existing mappings. For detailed procedures, see the following topics:
(Optional) In the Advanced tab, set any advanced mapping options.
(Optional) In the Comment tab, add a comment for the component.
The Property Mapper editor contains a unique name for this property mapper and a button that opens the Mappings editor, where you can view and modify mappings.
The Property Mapper editor contains the following tabs:
The Sources tab contains the following options:
Optional. The Record Index tab allows you to add or remove dimensions or properties used in a component's record index, and to change their order. Record indexes support join functionality. See Join sources must have matching join keys and record indexes for more details.
The Advanced tab contains the following options:
|
Option |
Description |
|---|---|
|
Map source properties to Endeca dimensions with the same name |
Check this field to enable implicit mapping. When implicit mapping is enabled, any source property that has a name that is identical to an existing dimension is automatically mapped to that dimension. (Implicit mapping only occurs if an explicit mapping is not specified. |
|
If no mapping is found, map source properties to Endeca |
Check this field to enable default mapping . Default mapping defines how Forge will handle source properties that have neither explicit nor implicit mappings. |
|
Default maximum length |
(Optional) Specifies the maximum source property value length allowed when creating mappings. Source properties that have values that exceed this length are not mapped, and a warning is issued by the Forge Hierarchical Logging system. If this field is left blank, the default is to not limit Endeca property mappings, and to limit dimension mappings to 255 characters. |
All property mappings are visable in the Property Mapper editor of each property mapper. Create new mappings, modify, or remove existing mappings.
To view existing property mappings in your project:
Note
A single source property can be mapped to multiple targets, including a mix of properties and dimensions. A single target can also be mapped from multiple sources.
